"Juozas Baliuka" <[EMAIL PROTECTED]> writes: > Databases lock updated and deleted rows only and transaction blocks > on conflict only, it never block query or not conflictiong updates, > I see three ways to solve update conflict:
> 1) block transaction > 2) abort transaction > 3) no concurent transactions > Looks like 3 is prefered in Prevayler, is not it ? Right. Interestingly, there is no performance hit to (3) *if* all your data is in memory. Oracle is a multi-billion dollar company mainly because this is rarely a valid assumption. I'm wondering if a weaker assumption (only live data must be in memory) would work for a somewhat larger portion of the applications people are using databases for. - a -- "Education is not filling a bucket but lighting a fire." -- WB Yeats ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
