Read-only transactions

Read-Only = "True | false" often appears in the Spring transaction configuration file or annotation attribute. The specific explanations are as follows:

 

 

1. Spring documents describes:

 

Read-Only status: a read-only transaction does not modify any data. Read-only transactions can be a useful Optimization in some cases (such as when using hibernate ).

2. From Google

 

If the transaction is marked as read-only, spring will set the hibernate session's flush mode to flush_never, and will set the JDBC transaction to read-only.

 

3. hiberante

 

When a session's flush mode is set to flush_never, two things happen:

First, running hql queries no longer cause hibernate to flush the session state to the database, which can provide a dramatic performance improvement.

Secondly, Hibernate will not flush the changes before commiting the transaction. But the user can still call session. Flush () by hand, causing any modifications to be persisted to database.

 

4. Oracle

 

When using the oracle JDBC driver, calling connection. setreadonly (true) translates into the statement "SET transaction read only ". this statement limits the types of SQL statements that can be executed during the transaction. only selects (without 'For Update') and a few other statements can be executed. specifically, no updates, deletes, inserts or merges can be executed. this behavior is Oracle-specific. other RDBMS can have different semantics for read only transactions or simply not support it at all.

 

 

 

From: http://www.codeinstructions.com/2009/04/read-only-transactions-with-spring-and.html