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:22:51 |
Message-ID: | 20020829192251.GA26316@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, Aug 29, 2002 at 12:11:09 -0700,
David Wheeler <david(at)wheeler(dot)net> wrote:
>
> 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.
That was in reference to that specific detail (doing begin immediately
rather than when needed), not the library as a whole.
I actually use DBI and in some things I am doing for work I use both
DBI and Pg in the same perl script (that talks to both oracle and postgres).
> BTW, the relatively new DBI begin_work() method may have overcome the
> issue you raise.
Thanks for this information.
From | Date | Subject | |
---|---|---|---|
Next Message | Vilson farias | 2002-08-29 19:59:18 | Some timestamp problems |
Previous Message | David Wheeler | 2002-08-29 19:17:16 | Re: Silencing NOTICEs in Perl Pg |