Re: Newbie to Postgres - Urgent query

From: Dustin Sallings <dustin(at)spy(dot)net>
To: Ritu Khetan <ritu(at)netcore(dot)co(dot)in>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Newbie to Postgres - Urgent query
Date: 2004-01-16 17:48:16
Message-ID: 299F740A-484C-11D8-A1D5-000393CFE6B8@spy.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Jan 16, 2004, at 1:18, Ritu Khetan wrote:

> $dbh = DBI->connect(DBI:Pg:dbname=dbname, $user_name, $password, {
> RaiseError => 0, PrintError => 0, AutoCommit => 0});

I've managed to avoid perl for a very long time now, but doesn't
RaiseError => 0 turn off the feature that causes DBI to actively tell
you when you've done something wrong rather than you having to ask
every time you do something if you did it correctly and it was
successful (which you're also not doing)?

Perhaps it's just style, but I can't think of any case where I'd want
normal execution to continue upon DB error without explicit code to
handle the situation. Likewise, I certainly wouldn't want to bother
writing extra code every time I require something to succeed.

--
Dustin Sallings

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Eric Ridge 2004-01-16 17:57:07 Re: Best Practice for incremental development
Previous Message Ben Ramsey 2004-01-16 17:36:57 Adding long text to a database text field generates errors