SCM

[#1011340] wrong results after CommandTimeout/Rollback()

View Trackers | Bugs | Download .csv | Monitor

Date:
2013-05-31 15:21
Priority:
3
State:
Open
Submitted by:
Johannes Abt (jsa)
Assigned to:
Nobody (None)
Npgsql Version:
2.0.12beta
Category:
None
Group:
None
Resolution:
None
Summary:
wrong results after CommandTimeout/Rollback()

Detailed description
Just after a long statement that was interrupted by the "CommandTimeout", I do a Rollback() on the transaction. (This causes another exception.) A subsequent trivial query ("select 5533::integer") returns null instead of the expected number.

To put in another way: The "CommandTimeout" not only causes an exception during executing the query ("ExecuteNonQuery()"), but during "Rollback()", too. Probably Rollback() forgets to read some message that the server has sent concerning the rollback operation. So the next query ("select 5533") reads an oudated message from the wire.

The only work around seems to be to close the connection when there is a error during "Rollback()".


Followup

Message
Date: 2013-06-18 21:49
Sender: Francisco Figueiredo jr.


Hi!

I think your problem is the same as this other one: http://pgfoundry.org/tracker/index.php?func=detail&aid=1011310&group_id=1000140&atid=590

If so, I already applied a patch to source code. Please give it a try and let me know.

Code is located at github: http://git.npgsql.org

Attached Files:

Attachments:
Program.cs

Changes:

Field Old Value Date By
File Added806: Program.cs2013-05-31 15:21jsa
Powered By FusionForge