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

blockIterators mechanism does NOT require allocating new cursor #118

Open
GoogleCodeExporter opened this issue Apr 8, 2016 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Another advantage of the new blockIterators iteration mechanism is that it 
actually doesn't require allocating a new cursor for each iterator.  
blockIterators has built-in query isolation, so no need to allocate a new 
cursor for each iterator.  

We could consider NOT allocating a new cursor for the blockIterators 
mechanism; this might make things a little more efficient (no need to keep 
opening and closing cursors for each iterator).

Original issue reported on code.google.com by cjlee...@gmail.com on 11 Sep 2009 at 5:28

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