Re: Silencing NOTICEs in Perl Pg - Mailing list pgsql-admin

From David Wheeler
Subject Re: Silencing NOTICEs in Perl Pg
Date
Msg-id 13A687F0-BB83-11D6-B671-0003931A964A@wheeler.net
Whole thread Raw
In response to Re: Silencing NOTICEs in Perl Pg  (Bruno Wolff III <bruno@wolff.to>)
Responses Re: Silencing NOTICEs in Perl Pg
Re: Silencing NOTICEs in Perl Pg
List pgsql-admin
On Thursday, August 29, 2002, at 12:04  PM, Bruno Wolff III wrote:

> 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.

DBD::Pg is built with libpg, too, IIRC.

> 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.

Hrm, I've never head DBI called "lame" before. But its advantages lie
in its standardization of database access. But yes, some might consider
that a limitation.

BTW, the relatively new DBI begin_work() method may have overcome the
issue you raise.

Regards,

David

--
David Wheeler                                     AIM: dwTheory
david@wheeler.net                                 ICQ: 15726394
http://david.wheeler.net/                      Yahoo!: dew7e
                                                Jabber: Theory@jabber.org


pgsql-admin by date:

Previous
From: Michael Zouroudis
Date:
Subject: Ref Int DELETE
Next
From: Bruno Wolff III
Date:
Subject: Re: Silencing NOTICEs in Perl Pg