From: Tim Bunce <Tim.Bunce@pobox.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David Wheeler <david@wheeler.net>
Cc: dbi-dev@perl.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: DBD::PostgreSQL
Date: Mon, 18 Nov 2002 16:39:08 +0000
Message-ID: <20021118163908.GD1444@dansat.data-plan.com> (raw)
In-Reply-To: <29660.1037636365@sss.pgh.pa.us>
References: <0907BA9A-FB11-11D6-93B3-0003931A964A@wheeler.net>
<29660.1037636365@sss.pgh.pa.us>
On Mon, Nov 18, 2002 at 11:19:25AM -0500, Tom Lane wrote:
> David Wheeler <david@wheeler.net> writes:
> > On Sunday, November 17, 2002, at 10:15 PM, Tom Lane wrote:
> >> Both of these seem pretty bogus to me. Ideally the driver should not
> >> issue a "begin" until the application issues the first command of the
> >> new transaction. Otherwise you get into scenarios where idle
> >> connections are holding open transactions, and ain't nobody gonna be
> >> happy with that.
>
> > Okay. I think I'll use a flag in the driver to track when it's in a
> > transaction, and do the right thing in the begin and rollback functions.
>
> I think someone else said that the DBD framework already includes such a
> flag ("BegunWork"?) --- if so, you should surely use that one.
BegunWork _only_ relates to the begin_work method. It's not used unless
that method is used, so it's not appropriate for your use here.
Just add a flag to the drivers private structure.
Tim.
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: Tim.Bunce@pobox.com, tgl@sss.pgh.pa.us, david@wheeler.net, dbi-dev@perl.org
Subject: Re: DBD::PostgreSQL
In-Reply-To: <20021118163908.GD1444@dansat.data-plan.com>
* 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