Re:iBATIS transactional behaviour

[ooper]

I suspect it depends on the rdbms being used and how it is configured; row level locks, page level locks, table level locks. I'm not
sure this is affected by iBATIS.

Scenario 1: Thread2 will be able to start a tx, but may have to wait for Thread1 to commit/rollback before it can commit/rollback.
This depends on locking mechanism on the table(s). If the entire table is locked, thread2 will be waiting. If a row is locked, thread2
may be able to run simultaneously, granted the same row is not being updated.

Scenario 2: Depends on locking mechanism of involved tables, and whether the affected rows in thread1 and thread2 are the same.

Scenario 3: No, they are separate and distinct transactions.

I'd suggest reading up on how transactions and locking are handled by your rdbms.

Brian Barnett


------------------------------------------------------------------------------------------------------------------------------------------------
Broadband interface (RIA) + mail box saftey = iBatis_for_Java_Users_List.roomity.com
*Your* clubs, no sign up to read, ad supported; try broadband internet. ~~1131151519724~~
------------------------------------------------------------------------------------------------------------------------------------------------