Received: from p2272.nsk.ne.jp (p2272.nsk.ne.jp [210.145.18.145]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f1AELmx53708; Sat, 10 Feb 2001 09:21:49 -0500 (EST) (envelope-from Inoue@tpf.co.jp) Received: from mcadnote1 (ppm251.noc.fukui.nsk.ne.jp [210.161.188.126]) by p2272.nsk.ne.jp (8.9.3/3.7W-20000722) with SMTP id XAA11373; Sat, 10 Feb 2001 23:21:00 +0900 (JST) From: "Hiroshi Inoue" To: "Hiroki Kataoka" Cc: , , "Steve Wranovsky" Subject: RE: 7.1 beta 3 Linux ODBC BEGIN Behaviour Date: Sat, 10 Feb 2001 23:22:19 +0900 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Archive-Number: 200102/80 X-Sequence-Number: 1033 > -----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