Re: dbi error handling

in reply to dbi error handling

select count(*) from table will always have at least one row: an empty table will give 0. (Of course, the table must exist, and the $dbh must be valid).

selectrow_array is just a convenience (it does a combined prepare + execute) for just this kind of SQL where you can be sure there will not be too many rows.

I'd say RaiseError => 1 is indeed the best and easiest way.

Comment on Re: dbi error handling

Replies are listed 'Best First'.
Re^2: dbi error handling by runrig (Abbot) on Dec 21, 2010 at 17:02 UTC
I've started the habit of using: `HandleError => sub { Carp::confess($_[0]) },` [download] in my connect() code. I started doing this because some versions of DBD::Sybase don't report the line number of the error with just RaiseError set (because the error messages had a newline on the end of them). Also, it's just nice to have a stack trace when a DBI call fails from deep within your function calls.	[reply] [d/l]
Re^3: dbi error handling by Anonymous Monk on Dec 22, 2010 at 03:31 UTC
Could you explain that a little bit more (I'm a perl beginner) please? Where does that code go? thanks	[reply]
Re^3: dbi error handling by Anonymous Monk on Dec 22, 2010 at 04:01 UTC
I've seen this in the dbi docs `http://search.cpan.org/~timb/DBI-1.615/DBI.pm#HandleError` [download] What data is in $_[0]	[reply] [d/l]
Re^4: dbi error handling by runrig (Abbot) on Dec 22, 2010 at 18:16 UTC
Huh, I didn't see that in the docs before (or forgot about it). `$_[0]` is the first argument to the function, i.e. the first element of the @_ array.	[reply] [d/l]

In Section Seekers of Perl Wisdom