RE: 7.1 beta 3 Linux ODBC BEGIN Behaviour - Mailing list pgsql-interfaces

From Hiroshi Inoue
Subject RE: 7.1 beta 3 Linux ODBC BEGIN Behaviour
Date
Msg-id EKEJJICOHDIEMGPNIFIJGEAKDJAA.Inoue@tpf.co.jp
Whole thread Raw
In response to RE: 7.1 beta 3 Linux ODBC BEGIN Behaviour  ("Hiroki Kataoka" <kataoka@interwiz.koganei.tokyo.jp>)
Responses Re: 7.1 beta 3 Linux ODBC BEGIN Behaviour  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-interfaces
> -----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

pgsql-interfaces by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Plan for straightening out the include-file mess
Next
From: Tom Lane
Date:
Subject: Re: 7.1 beta 3 Linux ODBC BEGIN Behaviour