From: Hiroshi Inoue <Inoue@tpf.co.jp>
To: Steve Wranovsky <stevew@merge.com>
Cc: L? zl?Tibor <ltibor@mail.tiszanet.hu>
Cc: kataoka@interwiz.koganei.tokyo.jp
Cc: pgsql-interfaces@postgresql.org
Cc: pgsql-odbc@postgresql.org
Subject: RE: 7.1 beta 3 Linux ODBC BEGIN Behaviour
Date: Sat, 10 Feb 2001 08:10:57 +0900
Message-ID: <EKEJJICOHDIEMGPNIFIJMEPFDIAA.Inoue@tpf.co.jp> (raw)
In-Reply-To: <4.3.2.7.2.20010209102114.00b5a900@mail.merge.com>
> -----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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: Inoue@tpf.co.jp, stevew@merge.com, ltibor@mail.tiszanet.hu, kataoka@interwiz.koganei.tokyo.jp, pgsql-odbc@postgresql.org
Subject: RE: 7.1 beta 3 Linux ODBC BEGIN Behaviour
In-Reply-To: <EKEJJICOHDIEMGPNIFIJMEPFDIAA.Inoue@tpf.co.jp>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox