isn't SELECT FOR UPDATE an Oracle-ism? instead of either entity locking or S-F-U, why not use an optimistic concurrency scheme, with verified updates? there was recently a nice catfight on the EJB-INTEREST mailing list between several vendors on this subject, the result of which seemed to be that this would be the approach which maximized both performance and portability. -- joe _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
- [JBoss-dev] ditch entity locking in favor of <select-for... Bill Burke
- Re: [JBoss-dev] ditch entity locking in favor of <s... Joseph Dane
- Re: [JBoss-dev] ditch entity locking in favor of &... Scott M Stark
- Re: [JBoss-dev] ditch entity locking in favor of &... David Jencks
- [JBoss-dev] Optimisitic locking vs. the rest... Bill Burke
- Re: [JBoss-dev] Optimisitic locking vs. the re... David Jencks
- Re: [JBoss-dev] Optimisitic locking vs. the re... Georg Rehfeld
- Re: [JBoss-dev] ditch entity locking in favor of <s... Rickard Öberg
- RE: [JBoss-dev] ditch entity locking in favor of &... Bill Burke
- Re: [JBoss-dev] ditch entity locking in favor ... Dain Sundstrom
- RE: [JBoss-dev] ditch entity locking in fa... Bill Burke
- RE: [JBoss-dev] ditch entity locking in fa... Sacha Labourey