Re: Silencing NOTICEs in Perl Pg

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: David Wheeler <david(at)wheeler(dot)net>
Cc: "David F(dot) Skoll" <dfs(at)roaringpenguin(dot)com>, Andrew Perrin <clists(at)perrin(dot)socsci(dot)unc(dot)edu>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Silencing NOTICEs in Perl Pg
Date: 2002-08-29 19:04:27
Message-ID: 20020829190427.GA25628@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, Aug 29, 2002 at 11:33:22 -0700,
David Wheeler <david(at)wheeler(dot)net> wrote:
> On Thursday, August 29, 2002, at 11:29 AM, David F. Skoll wrote:
>
> >PostgreSQL comes with its own "Pg" module, completely unrelated to DBI.
> >That's what I'm using.
>
> Oh, never noticed that before.
>
> May I suggest to the PostgreSQL developers that this be deprecated in
> favor of DBI/DBD::Pg? That really is the standard way to interface to
> databases in Perl.

Just because it is the standard way doesn't mean its the best way.
Pg is tied closely to libpg which may provide advantages in some cases.

For example, I believe DBI has a lame way to do things when autocommit is off.
It immediately starts a transaction rather than wait for a begin statement
to be sent. This has consequences that may not always be desirable.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message David Wheeler 2002-08-29 19:11:09 Re: Silencing NOTICEs in Perl Pg
Previous Message Michael Zouroudis 2002-08-29 18:59:28 Ref Int DELETE