Documentation for selective READ_COMMITTED transaction isolation using RW lock

moremore0812 / cqengine

Automatically exported from code.google.com/p/cqengine

0 stars 0 forks source link

Documentation for selective READ_COMMITTED transaction isolation using RW lock #30

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

CQEngine currently supports selective (per write, per query, or global) 
READ_COMMITTED transaction isolation, if the application takes care to 
demarcate its transactions using a ReadWriteLock.
This was discussed in the forum: 
https://groups.google.com/forum/#!topic/cqengine-discuss/9jIo0y5RDHA

Although it was discussed in the forum, the approach should be documented 
properly on a wiki page.

Original issue reported on code.google.com by ni...@npgall.com on 21 Dec 2013 at 2:28

GoogleCodeExporter commented 9 years ago

Original comment by ni...@npgall.com on 21 Dec 2013 at 2:31

Added labels: Type-Other
Removed labels: Component-Docs

GoogleCodeExporter commented 9 years ago

This is done in TransactionIsolation.
Multi-Version Concurrency Control (MVCC) is also supported.

Original comment by ni...@npgall.com on 20 Apr 2015 at 8:22

Changed state: Done