Devart Forums

Hi,

if you change data within a transaction and then call the Commit() member function of the PgSqlTransaction object, the "Default Command Timeout" value from the ConnectionString of the PgSqlConnection object is ignored. As a result, the Commit() can take a long time or never comes back, if the Transaction is blocked by another transaction for example.

Am i missing something? Or is this a feature? Is there a workaround?

We use
- Devart.Data.PostgreSql 6.6.242.0 and
- Devart.Data 5.0.701.0

In earlier versions of the connector (CoreLab.PostgreSql 3.25.20) this error was'nt there.

Regards,
pleach

We have changed the behavior. At the requests of our users, Command timeout does not affect transactions any more. This was implemented for committing big transactions. We will investigate the possibility to add the Timeout property for transactions.

We have implemented the CommitTimeout property of the PgSqlConnection object to determine timeout period for the Commit method. We will post here when the corresponding build of dotConnect for PostgreSQL is available for download.

Good news, thank you very much!

Regards,
pleach

The new build of dotConnect for PostgreSQL 6.6.267 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=27384