Message-ID: <3A886ED0.184C7B12@tpf.co.jp>
Date: Tue, 13 Feb 2001 08:16:32 +0900
From: Hiroshi Inoue <Inoue@tpf.co.jp>
MIME-Version: 1.0
To: Steve Wranovsky <stevew@merge.com>
CC: pgsql-interfaces@postgresql.org, pgsql-odbc@postgresql.org
Subject: Re: [ODBC] RE: 7.1 beta 3 Linux ODBC BEGINBehaviour
References: <3976.981826245@sss.pgh.pa.us>
	<4.3.2.7.2.20010212102302.00bca7c0@mail.merge.com>
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

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