Re: RE: [INTERFACES] 7.1 beta 3 Linux ODBC BEGINBehaviour - Mailing list pgsql-odbc

From Hiroshi Inoue
Subject Re: RE: [INTERFACES] 7.1 beta 3 Linux ODBC BEGINBehaviour
Date
Msg-id 3A886ED0.184C7B12@tpf.co.jp
Whole thread Raw
In response to Re: [INTERFACES] 7.1 beta 3 Linux ODBC BEGIN Behaviour  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-odbc
Steve Wranovsky wrote:
>
> >>
> >> Given these considerations, I think it's a mistake for ODBC to treat
> >> SELECT differently from other queries for the purpose of setting
> >> transaction boundaries.
> >>
> >
> >OK, agreed.
> >However simply putting back the behabior make it impossible to call
> >VACUUM in psqlodbc autocommit off mode.
> >
> >My idea is as follows.
> > [In autocommit off mode]
> > 1) All statements except STMT_TYPE_OTHER issue
> >     "BEGIN" if a trasaction isn't in progress.
> > 2) STMT_TYPE_OTHER statements automatically issue
> >    "COMMIT" if a transaction is progress.
> >
> >Comments ?
>
> I now agree with point 1 above, but for point 2, I believe you should
> force the user to issue a COMMIT if a transaction is in progress
> when they try a VACUUM ANALYZE.

I've been waiting for reply.
I see. It's the simplest change. But you seem to have to
change your existent your code. Or you may have to distinguish
your code according to PG servers. Is it OK ?

Regards,
Hiroshi Inoue

pgsql-odbc by date:

Previous
From: Steve Wranovsky
Date:
Subject: Re: RE: [INTERFACES] 7.1 beta 3 Linux ODBC BEGIN Behaviour
Next
From: Hiroshi Inoue
Date:
Subject: Re: RE: [PATCHES] Re: [HACKERS] 6.2 protocol