matevzm wrote
> I am getting error *"WARNING: there is already a transaction in progress"*
> when trying to execute command "*BEGIN TRANSACTION; LOCK TABLE "%s" IN
> EXCLUSIVE MODE;'"*
>
> We have written mutex which is working on other systems to unlock and lock
> database table using pgsql-odbc driver. Is that possible that transaction
> is ran automatically by driver or when "*cur *=* self.conn.cursor*()" is
> executed ? Has anyone else experienced that
This is exactly what is happening. You are being warned (not a failure)
that you are issuing BEGIN after the driver has issued BEGIN. The ODBC
driver provides the user the option to auto commit or not but fundamentally
in ODBC you are always in a transaction. The lack of warnings by other
drivers is the probable reason you haven't noticed your redundancy until
now.
David J.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/WARNING-there-is-already-a-transaction-in-progress-tp5811280p5811288.html
Sent from the PostgreSQL - odbc mailing list archive at Nabble.com.
