> The OJB isolation levels *do not* touch the db! They only concern the ODMG object >level tx management. The isolation levels of the underlying RDBMS are not used by >OJB! <
OK, now I am really confused. What do you mean by "OJB isolation levels?" Are you not referring to java.sql.connection.setTransactionIsolation(int level)? Unless OJB is using some magic that I am unaware of, "RDBMS isolation levels" ARE always used, at least the default isolation level for the specific RDBMS. Does this have anything to do with the LOCK TABLE sql command I heard OJB used? Obviously there is a information gap on my part here. If you can, please point me to where I can go to read more about this. Thanks, Jeff Boring Custom & Web Services Development AT&T Labs [EMAIL PROTECTED] -----Original Message----- From: Mahler Thomas [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 8:16 AM To: 'OJB Users List' Subject: RE: ODMG and locking (follow up) Hi, > > I read this tread about locking and want to make sure I > understand object > cache locking verses RDBMS locking. Locking as discussed in that tread > (implicit) as well the as org.apache.ojb.odmg.locking > interface has to do > with the object cache, not share/exclusive locks applied to > the rows of the > database (for RDBMS with row level locking)? Right? Correct! > RDBMS locking is > controlled solely by the isolation level and the specific DML > issued, right? > The OJB isolation levels *do not* touch the db! They only concern the ODMG object level tx management. The isolation levels of the underlying RDBMS are not used by OJB! cheers, Thomas > Jeff W Boring > [EMAIL PROTECTED] > 813.878-3367 (work) > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
