[Pypgsql-devel] [ pypgsql-Bugs-1041283 ] Transaction must not be aborted in case of OperationalError

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

Bugs item #1041283, was opened at 2004-10-06 11:23
Message generated for change (Comment added) made by peergriebel
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116528&aid=1041283&group_id=16528

Category: PgSQL
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Peer (peergriebel)
Assigned to: Nobody/Anonymous (nobody)
Summary: Transaction must not be aborted in case of OperationalError

Initial Comment:
I'm using 
    SET statement_timeout to xxx
for my database connection.
If this timeout is reached the processing of the
statement is canceled with an OperationalError.
This error is caught by Cursor.execute() which in turn
performs a ROLLBACK WORK.

If I understand correctly the a statement timeout is
_not_ a fatal error. So the transaction must not be
rolled back.

I would like to see this behaviour explained/fixed.

Thank you!

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

>Comment By: Peer (peergriebel)
Date: 2004-10-06 13:41

Message:
Logged In: YES 
user_id=1133977

The same applies to an OperationalError as a result of an
error stating "Cannot insert a duplicate key into unique
index ...". This also seems not to be fatal. Nonetheless the
transaction is aborted.

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

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