In the following article on Sessions and Transactions
http://www.hibernate.org/42.html#A3
Session-per-conversation pattern for long running application transaction doesn't say anything about nature of each transaction, ie. update or read.
In nHibernate documentation under 10.4. Optimistic concurrency control here's what I read:
Quote:
Maintaining isolation of business processes becomes the partial responsibility of the application tier, hence we call this process a long running application transaction. A single application transaction usually spans several database transactions. It will be atomic if only one of these database transactions (the last one) stores the updated data, all others simply read data.
Since in session-per-conversation pattern all changes are flushed when long conversation/application transaction ends, statement from 10.4 on Optimistic concurrency control is not entirely accurate? Am I correct?
Andre
Login
FAQ
Search