JDatastore locks rows on the default transaction isolation level

Abstract: JDatastore locks rows on the default transaction isolation level

Product: JDatastore
Version: 6.x, 7.x


Question:

When using the default transaction isolation level (TRANSACTION_READ_COMMITTED) an insert into a table, blocks queries selecting all rows on the same table, until commit or rollback is performed.


Answer:

JDataStore's read only transactions do not block for any locks and do not block other read/write transactions.�

This makes them ideal for long running reports or browsing of data with a high amount of contention from read/write transactions.�

The read only transactions provide a transactionally consistent view of the database from the time the transaction started.