| From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Mike Miller <mmiller(at)pooka(dot)otago(dot)ac(dot)nz> |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: ODBC & Transactions? |
| Date: | 2001-11-08 00:47:00 |
| Message-ID: | 3BE9D604.78BFAC7D@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Mike Miller wrote:
>
[snip]
>
> <SPECULATION>
> It *looks* to me like something is wrapping all the queries in a
> transaction. Is this an autocommit feature? If so, is it from ODBC or
> postgres itself. How does one turn it off - apparently "BEGIN WORK" *does
> not* turn it off...
> </SPECULATION>
CommitTransactionCommand doesn't necessarily mean COMMIT.
You have to use BeginTrans to turn of the autocommit mode
but it doesn't seem the cause of your case(It works well
here). Judging from the psqlodbc.log file you posted,
"rollback work" is issued by the differenct connection
from the one which issued "begin work" and "update ...".
Hmm are you using connection pooling ?
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2001-11-08 00:58:36 | Re: ODBC and Native error codes |
| Previous Message | Mike Miller | 2001-11-07 21:08:17 | Re: ODBC & Transactions? |