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 f19NIPx36143; Fri, 9 Feb 2001 18:18:25 -0500 (EST) (envelope-from Inoue@tpf.co.jp) Received: from mcadnote1 (ppm116.noc.fukui.nsk.ne.jp [210.161.188.35]) by p2272.nsk.ne.jp (8.9.3/3.7W-20000722) with SMTP id IAA20761; Sat, 10 Feb 2001 08:09:34 +0900 (JST) From: "Hiroshi Inoue" To: "Steve Wranovsky" Cc: "L? zl?Tibor" , , , Subject: RE: 7.1 beta 3 Linux ODBC BEGIN Behaviour Date: Sat, 10 Feb 2001 08:10:57 +0900 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal In-Reply-To: <4.3.2.7.2.20010209102114.00b5a900@mail.merge.com> X-Archive-Number: 200102/78 X-Sequence-Number: 1031 > -----Original Message----- > From: Steve Wranovsky [mailto:stevew@merge.com] > > I would think you when a standard SELECT is issued, you would not want to > have a BEGIN, however, when a SELECT FOR UPDATE is issued, you may want > to issue the BEGIN in this case. > > Is it easy to discriminate between these types of selects to > decide when to > do the begin? > Unfortunately no(at least for me). The simplest solution is to simply issue BEGIN for all statements in autocommit off mode if transaction isn't in progress. However there are some commands(VACUUM etc) that couldn't be executed inside transaction blocks. Regards, Hiroshi Inoue