comment on

It's just an example. There are several things that can go wrong during database insertion or update, some of which depend on user input, so need to be registered as a form error.

In those cases the you'd get a list of catches, plus a catch-all that would just dump the actual error message

It would probably need a change right down at the DBD/DBI level, and the way the drivers register their error handlers

--
Lyon

In reply to Re^2: post mortem on DBI errors by redlemon
in thread post mortem on DBI errors by redlemon

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks