> -----Original Message-----
> From: Hiroshi Inoue [mailto:Inoue(at)tpf(dot)co(dot)jp]
> Sent: 12 February 2001 23:17
> To: Steve Wranovsky
> Cc: pgsql-interfaces(at)postgresql(dot)org; pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] RE: [INTERFACES] 7.1 beta 3 Linux 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 ?
I've not really been following this thread, but changing code or writing
server version dependant code sounds very bad to me. Certainly in my case I
have enough issues as it is keeping pgAdmin working with the current and
pgsql-odbc by date
|Next:||From: Hiroshi Inoue||Date: 2001-02-13 10:47:23|
|Subject: Re: [ODBC] RE: 7.1 beta 3 Linux ODBC BEGINBehaviour|
|Previous:||From: Hiroshi Inoue||Date: 2001-02-12 23:44:17|
|Subject: Re: RE: [PATCHES] Re: [HACKERS] 6.2 protocol|
pgsql-interfaces by date
|Next:||From: Peter T Mount||Date: 2001-02-13 10:00:03|
|Subject: Re: Problem with JDBC driver: rs.next() is always null|
|Previous:||From: Tom Lane||Date: 2001-02-13 00:37:52|
|Subject: Re: lo_creat problem? |