Re^2: SQLite handling of errors through common function

I downvoted this because the OP already uses RaiseError. The answer does not fit the question.

Comment on Re^2: SQLite handling of errors through common function

Replies are listed 'Best First'.
Re^3: SQLite handling of errors through common function by sundialsvc4 (Abbot) on Nov 06, 2013 at 19:02 UTC
So sue me for overlooking that. `O_o` ... (Not that I give a damn about “XP” anyway, but let’s just stay on-topic here.) Your eagle-eyed observation does raise a different point: my understanding is that the presence of this option will prevent the execution of the existing handler-routine in the OP’s example, because (IIRC) it will throw an exception in case of any error. The DBI-call won’t return a non-zero value ... it won’t return anything at all. Instead, the code will die, and I see no error-handling logic (not even a basic `eval{}`) in it. Which would definitely be a bug of a different sort.	[reply]
Re^4: SQLite handling of errors through common function by Anonymous Monk on Nov 06, 2013 at 20:23 UTC
So sue me for overlooking that. There is no suing on perlmonks; daxim already downvoted	[reply]
Re^4: SQLite handling of errors through common function by mje (Curate) on Nov 07, 2013 at 11:01 UTC
My understanding is the HandleError routine is called before DBI dies and the handler can actually alter what DBI does.	[reply]