As [id://perrin] mentioned, eval is the easiest way to catch these so the user doesn't see a nasty error. However, it might start to seem tedious to put eval blocks around all of your Class::DBI code.
This type of problem is one of the reasons several web app frameworks have popped up on CPAN. CGI::Prototyped, for example, wraps all of the main execution block in an eval. This allows you to build a single error handling sub that knows how to handle the error and display a nice page for the user. This solves the problem not only for Class::DBI 'dies' but allows you to use die throughout your code as a exception.
If you don't want to get into learning a web app framework, you could just steal the idea and put your eval at a high enough level that it catches everything that might die.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.