Bug: SET TRANSACTION ISOLATION LEVEL

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for PostgreSQL
Post Reply
bpipe
Posts: 19
Joined: Mon 08 Oct 2012 12:14

Bug: SET TRANSACTION ISOLATION LEVEL

Post by bpipe » Wed 31 Oct 2012 13:47

SET TRANSACTION ISOLATION LEVEL is called before BEGIN.

According to PostreSql documentation:
The SET TRANSACTION command sets the characteristics of the current transaction. It has no effect on any subsequent transactions.
If SET TRANSACTION is executed without a prior START TRANSACTION or BEGIN, it will appear to have no effect, since the transaction will immediately end.
http://www.postgresql.org/docs/9.2/stat ... ction.html

Pinturiccio
Devart Team
Posts: 2420
Joined: Wed 02 Nov 2011 09:44

Re: Bug: SET TRANSACTION ISOLATION LEVEL

Post by Pinturiccio » Fri 02 Nov 2012 13:27

We have reproduced the issue. We will investigate it and notify you about the results as soon as possible.

bpipe
Posts: 19
Joined: Mon 08 Oct 2012 12:14

Re: Bug: SET TRANSACTION ISOLATION LEVEL

Post by bpipe » Fri 02 Nov 2012 18:30

Great.

Also it would be nice if you could fix minor incorrect behavior with COMMIT called after PREPARE TRNSACTION, though this is not error, but this produces a WARNING in PostgreSQL log, which 1) pollutes log file, making it hard to read, 2) slow down performance, because for every transaction warning line have to be written.

Explanation: when PREPARE TRANSACTION statement is executed the current transaction is promoted to Prepared and it's no longer associated with current session (connection), it is no longer considered a current transaction, so calling COMMIT will produce a warning telling that there is no current transaction in progress, only COMMIT PREPARED statement is needed.

Quote from PostgreSQL documentation:
Issuing COMMIT when not inside a transaction does no harm, but it will provoke a warning message.

Pinturiccio
Devart Team
Posts: 2420
Joined: Wed 02 Nov 2011 09:44

Re: Bug: SET TRANSACTION ISOLATION LEVEL

Post by Pinturiccio » Mon 12 Nov 2012 10:56

We have fixed the bug with set transaction isolation level. We will post here when the corresponding build of dotConnect for PostgreSQL is available for download.

We will also investigate the behavior with COMMIT called after PREPARE TRANSACTION and notify you about the results as soon as possible.

Pinturiccio
Devart Team
Posts: 2420
Joined: Wed 02 Nov 2011 09:44

Re: Bug: SET TRANSACTION ISOLATION LEVEL

Post by Pinturiccio » Wed 14 Nov 2012 14:17

We have fixed the bug with executing COMMIT after COMMIT PREPARED with a distributed transaction. We will post here when the corresponding build of dotConnect for PostgreSQL is available for download.

Pinturiccio
Devart Team
Posts: 2420
Joined: Wed 02 Nov 2011 09:44

Re: Bug: SET TRANSACTION ISOLATION LEVEL

Post by Pinturiccio » Thu 15 Nov 2012 14:56

The new build of dotConnect for PostgreSQL 6.2.122 is available for download now!
It can be downloaded from http://www.devart.com/dotconnect/postgr ... nload.html (trial version) or from Registered Users' Area (for users with valid subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?t=25285

Post Reply