[Pypgsql-devel] [ pypgsql-Bugs-747525 ] Commit Invalidating Client-Side Cursors

[SourceForge.net <no...@so...>]

Bugs item #747525, was opened at 2003-06-02 09:35
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116528&aid=747525&group_id=16528

Category: PgSQL
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Michael Owens (owensmk)
Assigned to: Nobody/Anonymous (nobody)
Summary: Commit Invalidating Client-Side Cursors

Initial Comment:
This is a behavior issue. 
 
connection::commit() invalidates all cursors, even when 
noPostgresCursor = 1. Even though a transaction has completed, it 
seems uncessary to make data already stored in client-side cursors 
unreadable. As best I can tell, this behavior is not required by the specs 
either. 
 
I can understand why server-side cursors may have need of this, but it 
would be nice if client-side cursors could still be read. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116528&aid=747525&group_id=16528