[pygr-notify] Issue 118 in pygr: blockIterators mechanism does NOT require allocating new cursor

[codesite-noreply at google.com]

Status: New
Owner: pygr-bug... at googlegroups.com
Labels: Type-Enhancement Priority-Low

New issue 118 by cjlee112: blockIterators mechanism does NOT require  
allocating new cursor
http://code.google.com/p/pygr/issues/detail?id=118

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).

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings