Received: from sd.tpf.co.jp (sd.tpf.co.jp [210.161.239.34]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id f1951Cx71472 for ; Fri, 9 Feb 2001 00:01:12 -0500 (EST) (envelope-from Inoue@tpf.co.jp) Received: (qmail 14635 invoked from network); 9 Feb 2001 05:01:09 -0000 Received: from unknown (HELO viscomail.tpf.co.jp) (100.0.0.108) by sd2.10.0.100.in-addr.arpa with SMTP; 9 Feb 2001 05:01:09 -0000 Received: from tpf.co.jp (3d_note1 [126.0.1.61]) by viscomail.tpf.co.jp (8.8.8+Sun/8.8.8) with ESMTP id OAA01290; Fri, 9 Feb 2001 14:01:08 +0900 (JST) Message-ID: <3A8379DA.F098976@tpf.co.jp> Date: Fri, 09 Feb 2001 14:02:18 +0900 From: Hiroshi Inoue X-Mailer: Mozilla 4.73 [ja] (Windows NT 5.0; U) X-Accept-Language: ja MIME-Version: 1.0 To: Steve Wranovsky CC: pgsql-interfaces@postgresql.org, "pgsql-odbc@postgresql.org" Subject: Re: 7.1 beta 3 Linux ODBC BEGIN Behaviour References: <4.3.2.7.2.20010208124747.00c3e860@mail.merge.com> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Archive-Number: 200102/67 X-Sequence-Number: 1020 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. Regards, Hiroshi Inoue