Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation for selective READ_COMMITTED transaction isolation using RW lock #30

Open
GoogleCodeExporter opened this issue Jun 15, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

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
Copy link
Author

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

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

@GoogleCodeExporter
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant