Re: DBD::Pg 1.00

From: "Peter Haworth" <pmh(at)edison(dot)ioppublishing(dot)com>
To: newsreader(at)mediaone(dot)net, pgsql-general(at)postgresql(dot)org
Subject: Re: DBD::Pg 1.00
Date: 2001-06-01 09:33:26
Message-ID: PGM.20010601093326.16619.496@edison.ioppublishing.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 30 May 2001 12:54:17 -0400, newsreader(at)mediaone(dot)net wrote:
> On Wed, May 30, 2001 at 04:02:51PM +0100, Peter Haworth wrote:
> > On Wed, 30 May 2001 08:07:11 -0400, newsreader(at)mediaone(dot)net wrote:
> > The new behaviour is mre correct.
> >
>
> Why? The old behavior is better. Less coding.

It's also less compliant with the DBI spec. I suspect that this only works because the Postgres client library fetches the entire result set into memory. For other databases where it is not possible to fetch rows from an exhausted result set, the specified behaviour makes a lot more sense.

Also, this stops DBD::Pg complaining about destroying open statement handles. The DBI says that you don't need to explicitly finish statements after fetching all the rows, so this is good, too.

--
Peter Haworth pmh(at)edison(dot)ioppublishing(dot)com
"Ok, print the message, then put it in your shoe and put your shoe in front
of the fireplace... then wait till Santa come and give the code to you ;-)
Hey! this is not mod_santa list !"
-- Fabrice Scemama on the mod_perl list

In response to

Browse pgsql-general by date

  From Date Subject
Next Message newsreader 2001-06-01 09:59:58 Re: Re: dumping strategy
Previous Message fabrizio.ermini 2001-06-01 07:56:03 (Fwd) Majordomo Delivery Error