From: | Ed Loehr <eloehr(at)austin(dot)rr(dot)com> |
---|---|
To: | "pgsql-interfaces(at)postgreSQL(dot)org" <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | [INTERFACES] Re: [DELIVERY FAILURE: User laszlo_acs (laszlo_acs@cms.state.il.us)... |
Date: | 2000-03-07 14:50:01 |
Message-ID: | 38C51719.8306A08D@austin.rr.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Would one of the pgsql-interfaces list administrators consider
removing laszlo_acs(at)cms(dot)state(dot)il(dot)us from the pgsql-interfaces mailing
list? His mail is bouncing seemingly on every submission to the list.
Regards,
Ed Loehr
Postmaster(at)state(dot)il(dot)us wrote:
>
> Your message
>
> Subject: Re: [INTERFACES] Re: Quick perl question
>
> was not delivered to:
>
> laszlo_acs(at)cms(dot)state(dot)il(dot)us
>
> because:
>
> User laszlo_acs (laszlo_acs(at)cms(dot)state(dot)il(dot)us) not listed in public Name & Address Book
>
> ----------------------------------------------------------------------
> Reporting-MTA: dns;cms.state.il.us
>
> Final-Recipient: rfc822;laszlo_acs(at)cms(dot)state(dot)il(dot)us
> Action: failed
> Status: 5.1.1
> Diagnostic-Code: X-Notes; User laszlo_acs (laszlo_acs(at)cms(dot)state(dot)il(dot)us) not listed in public Name & Address Book
>
> ----------------------------------------------------------------------
>
> Subject: Re: [INTERFACES] Re: Quick perl question
> Date: Mon, 06 Mar 2000 14:33:15 -0600
> From: Ed Loehr <eloehr(at)austin(dot)rr(dot)com>
> To: <bweaver(at)tranquility(dot)net>
> CC: <pgsql-interfaces(at)postgreSQL(dot)org>
>
> > I also would like to echo the comments that someone else has made about using
> > DBI::DBD rather than Pg. Pg works well and is slightly easier to get working,
> > but that is because the complexity of DBI::DBD adds some useful stuff not
> > present in Pg. In particular, the error trapping is great. On the down side, it
> > gets tedious writting each query as two parts: "prepare" and "execute". This is
> > compensated for in overall portability to other DBMS, I think.
>
> You may also avoid that downside by encapsulating prepare() and
> execute(), eg.
>
> sub mySelect {
> ...
> prepare...
> execute...
> ...
> }
>
> Regards,
> Ed Loehr
>
> ************
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Verstak | 2000-03-07 15:19:42 | Re: [INTERFACES] Type mappings |
Previous Message | Michael Katkin | 2000-03-06 23:13:50 | delete katkin.1@osu.edu |