Re: BEGIN and autocommit(false) (was: some question about SavePoint ?) - Mailing list pgsql-odbc

From Ludek Finstrle
Subject Re: BEGIN and autocommit(false) (was: some question about SavePoint ?)
Date
Msg-id 20060119142412.GA13237@soptik.pzkagis.cz
Whole thread Raw
In response to BEGIN and autocommit(false) (was: some question about SavePoint ?)  (Marc Herbert <Marc.Herbert@continuent.com>)
List 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

pgsql-odbc by date:

Previous
From: Marc Herbert
Date:
Subject: BEGIN and autocommit(false) (was: some question about SavePoint ?)
Next
From: "lothar.behrens@lollisoft.de"
Date:
Subject: How to detect float format by passing SQL_CHAR to float column ?