| From: | merlyn(at)stonehenge(dot)com (Randal L(dot) Schwartz) |
|---|---|
| To: | Dustin Sallings <dustin(at)spy(dot)net> |
| Cc: | Ritu Khetan <ritu(at)netcore(dot)co(dot)in>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Newbie to Postgres - Urgent query |
| Date: | 2004-01-16 19:15:09 |
| Message-ID: | 8665fb66yq.fsf@blue.stonehenge.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>>>>> "Dustin" == Dustin Sallings <dustin(at)spy(dot)net> writes:
Dustin> Perhaps it's just style, but I can't think of any case where
Dustin> I'd want normal execution to continue upon DB error without explicit
Dustin> code to handle the situation. Likewise, I certainly wouldn't want to
Dustin> bother writing extra code every time I require something to succeed.
My DBI standard method is to call RaiseError => 1, PrintError => 0.
It just seems to make for easier to read code.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn(at)stonehenge(dot)com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Bergeron | 2004-01-16 19:22:19 | Re: [GENERAL] problem starting postmaster as a service |
| Previous Message | Aron Roberts | 2004-01-16 19:11:58 | plpythonu AKA am I crazy? or.... |