Re^3: error catching

RaiseError doesn't work for the initial ->connect statement. You need to check that one manually.

⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊

Comment on Re^3: error catching

Replies are listed 'Best First'.
Re^4: error catching by runrig (Abbot) on Dec 20, 2006 at 01:04 UTC
Yes, it does. Since 0.91.	[reply]
Re^5: error catching by diotalevi (Canon) on Dec 20, 2006 at 01:06 UTC
Oh. That hasn't been true in any DBI I've knowingly used. Maybe the feature just didn't work for several years. ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊	[reply]
Re^4: error catching by Joost (Canon) on Dec 20, 2006 at 01:05 UTC
I meant to say "use RaiseError as an option to the connect call", not as the check for the connect call. Anyway, don't most calls to an unconnected $dbh cause an exception? "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^5: error catching by diotalevi (Canon) on Dec 20, 2006 at 01:08 UTC
Yes. A failed ->connect call returns undef so there's no object that a method can be called upon. ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊	[reply]