From: | Ludek Finstrle <luf(at)pzkagis(dot)cz> |
---|---|
To: | Marc Herbert <Marc(dot)Herbert(at)continuent(dot)com> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: BEGIN and autocommit(false) (was: some question about SavePoint ?) |
Date: | 2006-01-19 14:24:12 |
Message-ID: | 20060119142412.GA13237@soptik.pzkagis.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> >> 1. set SQL_AUTOCOMMIT_OFF
> >
> > Yes you do ... When you use autocommit = off you have to start and end
> > transaction manually.
>
> Wrong: in ODBC, you just have to "end" transactions manually, you
> don't have to start them, they are implicitely started when the
> previous one ends.
>
> In ODBC (and JDBC), you are ALWAYS inside a transaction, there is no
> such thing as a transactional "no man's land" from an ODBC interface
> point of view (internal, hidden implementation details may differ).
Thanks a lot for showing me the rigth way. I was confused when
I touch the relevant code. It's clear for me now.
> Of course you can quite trivially implement one interface style _on
> top of_ the other, if ever needed. That is probably what pgodbc
> does/should do. That does not imply mixing the two concepts. Please.
Ok. I'll take a look at the code with this (for me) new informations.
Regards,
Luf
From | Date | Subject | |
---|---|---|---|
Next Message | lothar.behrens@lollisoft.de | 2006-01-19 15:27:09 | How to detect float format by passing SQL_CHAR to float column ? |
Previous Message | Marc Herbert | 2006-01-19 14:03:54 | BEGIN and autocommit(false) (was: some question about SavePoint ?) |