Well, don't make any efforts on my behalf just yet. If it had just been that one thing, I could have started the work myself :-)
The other blocker is true vertical inheritance support, and right now, there is no imminent urge to switch by project management. I just wanted to throw out a typical use case. On Wed, Nov 7, 2012 at 9:22 AM, Andrus Adamchik <[email protected]> wrote: > > On Nov 7, 2012, at 4:52 PM, Mike Kienenberger <[email protected]> wrote: > >>> Would be great if someone could share their typical use cases. >> >> We are not using Cayenne but JPA in my current project, but one of the >> items that we would need to address to convert from JPA to Cayenne is >> that we flush financial transactions to the database. > > A project desiring to switch to Cayenne, but lacking feature X usually > motivates me pretty well to get X in Cayenne (if X makes sense to us > otherwise) ;) > >> Basically an in-memory query where balances are computed at the current >> stage not >> only based on what's in the database, but what transactions are >> waiting to be committed to the database. I don't know the details of >> why we went this route but this is the big picture of our use case. > > You can wrap multiple context commits in a manual transaction with something > like "TRANSACTION_READ_UNCOMMITTED" isolation level. This is of course if > your multiple commits all happen in a short sequence (e.g. in the same > request). > > Andrus > > >
