Skip site navigation (1) Skip section navigation (2)

RE: 7.1 beta 3 Linux ODBC BEGIN Behaviour

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Hiroki Kataoka" <kataoka(at)interwiz(dot)koganei(dot)tokyo(dot)jp>
Cc: <pgsql-interfaces(at)postgresql(dot)org>, <pgsql-odbc(at)postgresql(dot)org>, "Steve Wranovsky" <stevew(at)merge(dot)com>
Subject: RE: 7.1 beta 3 Linux ODBC BEGIN Behaviour
Date: 2001-02-10 14:22:19
Message-ID: EKEJJICOHDIEMGPNIFIJGEAKDJAA.Inoue@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-interfacespgsql-odbc
> -----Original Message-----
> From: Hiroki Kataoka
> 
> Hiroshi Inoue wrote
> > 
> > Steve Wranovsky wrote:
> > > 
> > > Hello,
> > > 
> > > I found another slight behavior change with the Linux
> > > client ODBC library between 7.0.3 and the 7.1 beta 3
> > > release.  We are running under Redhat 6.0.
> > > 
> > > We have set the ODBC driver in autocommit off mode.  With
> > > the 7.0.3 driver, a BEGIN was automatically issued
> > > before the driver encountered a INSERT/UPDATE/DELETE.  With
> > > the 7.1 beta 3 ODBC driver, it now also issues a BEGIN when it
> > > encounters a SELECT.
> > > 
> > > Is this the expected behavior under 7.1?
> > 
> > Probably not.
> > I would put back the behabior in a few days. 
> 
>   There must be "SELECT ~ FOR UPDATE" of inside of the transaction.
> 

You are right.
However psqlodbc has never checked "for update".
My recent change doesn't take "for update" into
account either. 
You know psqlodbc much more than me.
Could you make a patch for it ?
Or could you suggest how to do it ?

Regards,
Hiroshi Inoue

In response to

Responses

pgsql-odbc by date

Next:From: Bruce MomjianDate: 2001-02-10 15:15:54
Subject: Re: RE: [PATCHES] Re: [HACKERS] 6.2 protocol
Previous:From: Hiroshi InoueDate: 2001-02-10 14:21:37
Subject: RE: [PATCHES] Re: [HACKERS] 6.2 protocol

pgsql-interfaces by date

Next:From: Tom LaneDate: 2001-02-10 17:30:45
Subject: Re: 7.1 beta 3 Linux ODBC BEGIN Behaviour
Previous:From: SashaDate: 2001-02-10 13:09:44
Subject: Problem with JDBC driver: rs.next() is always null

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group