on 8/21/01 2:00 AM, "Jason Grant" <[EMAIL PROTECTED]> wrote:
> I've read all the posts relating to Torque & how to perform transactions,
> but am still unclear on how to solve concurrency & data integrity issues
> with Torque and mysql. My understanding is that mysql always commits
> when each statement is complete. I assume that use of
> o.a.t.u.db.adapter.DB.lockTable() for this purpose is bad practice if the
> same code is to be portable with other databases which do support
> transactions? Should I be adding synchronized OM methods, or perhaps
> trying to implement row locks within peer classes? Again, these don't
> seem like a good portable solutions.
>
> I'm also puzzled because I can't see how scarab prevents database race
> conditions, so suspect that I'm missing something obvious...
MySQL does not support transactions unless you have the BerkeleyDB stuff
compiled in and running and the database driver you are using properly makes
the right calls to MySQL.
thanks,
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
