From: | Hartmut Raschick <hartmut(dot)raschick(at)ke-elektronik(dot)de> |
---|---|
To: | "postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
Subject: | unnecessary auto-transaction-rollback from driver - part 2 of 2 |
Date: | 2003-08-29 06:50:38 |
Message-ID: | 3F4EF7BE.198B178D@ke-elektronik.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
PLEASE MIND part 1 (another mail)
driver: psqlodbc-07.03.0100
postgres: 7.3.2
error messages: n/a
mylog: mylog_raschick10724.log
commlog(psqlodbc_????.log): psqlodbc_raschick10724.log
ODBC trace log (sql.log): n/a
when issuing (w/i a transaction) a faulty request (in this case: attempt to
set a column that does not exist) the driver will auto-rollback (see logs).
however, as the program has started the transaction, it will try to rollback
itself. this will fail. (you see this twice in the logs - dont worry, one is
destructor clean-up...)
IMHO, the driver should not do a rollback here.
while inspecting the sources, i found that it actually knows about being in
a trx (succesful "BEGIN" command), why it would not use this info, i dont
know...
P.S.:
--
Hartmut "Hardy" Raschick / Dept. t2
ke Kommunikations-Elektronik GmbH
Wohlenberstr. 3, 30179 Hannover
Phone: ++49 (0)511 6747-564
Fax: ++49 (0)511 6747-340
e-Mail: hartmut(dot)raschick(at)ke-elektronik(dot)de
http://www.ke-elektronik.de
Attachment | Content-Type | Size |
---|---|---|
psqlodbc-07.03.0100-auto-rollback-part2of2.tar.gz | application/x-gzip | 3.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Hartmut Raschick | 2003-08-29 07:01:06 | unnecessary auto-transaction-rollback from driver - part 1 of 2 |
Previous Message | Brian J. Erickson | 2003-08-28 18:23:33 | ODBC, SQLExecute and HY010 |