From: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | David Wheeler <david(at)wheeler(dot)net>, dbi-dev(at)perl(dot)org, pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: DBD::PostgreSQL |
Date: | 2002-11-18 16:39:08 |
Message-ID: | 20021118163908.GD1444@dansat.data-plan.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
On Mon, Nov 18, 2002 at 11:19:25AM -0500, Tom Lane wrote:
> David Wheeler <david(at)wheeler(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Jason Hihn | 2002-11-18 16:39:57 | Re: Press Release -- Just Waiting for Tom |
Previous Message | Zeugswetter Andreas SB SD | 2002-11-18 16:32:25 | Re: [GENERAL] DECLARE CURSOR |
From | Date | Subject | |
---|---|---|---|
Next Message | David Wheeler | 2002-11-18 16:42:01 | Re: DBD::PostgreSQL |
Previous Message | David Wheeler | 2002-11-18 16:27:33 | Re: DBD::PostgreSQL |