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.

Sign up for GitHub

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

Jump to bottom

Multiversion concurrency control(MVCC) should be implemented for transaction isolation #36

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

Multiversion concurrency control(MVCC) should be implemented for transaction isolation #36

GoogleCodeExporter opened this issue Jun 15, 2015 · 2 comments
Labels
auto-migrated Priority-Medium Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

Multiversion concurrency control(MVCC) should be implemented for transaction 
isolation handling.

Lock is not an efficient solution if performance and consistency is important.

Original issue reported on code.google.com by harry.ca...@gmail.com on 27 Apr 2014 at 10:15
@GoogleCodeExporter
Copy link
Author 

Implementing MVCC is on my radar. In the meantime, patches are welcome.

Changing type from defect -> enhancement as this is not a bug.

Original comment by ni...@npgall.com on 25 Nov 2014 at 10:37

  • Changed state: Accepted
  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author 

Implemented in CQEngine 2.0.

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

  • Changed state: Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter