re: DBI error handling, I left it out of my example code snippet, but I tested with using the "or die" idiom you showed.

However, it doesn't fire off the die. Strangely, that statement seems to work just fine. It just taints in the $dbh in some way I can't put my finger on yet.

For what its worth, in terms of a more global error handling scheme for DBI I find the die's of RaiseError to be a little too drastic. Instead, I wire in my own error handling scheme, ie:

$dbh->{'HandleError'}=\&dbierror;

re: Possible CGI::Session bug, I scanned the modules RT queue and noted another utf8 related problem that's still open. Maybe I can help push along its resolution...

Thanks for your input!

In reply to Re^2: CGI::Session and UTF-8 with Mysql? by pffan239
in thread CGI::Session and UTF-8 with Mysql? by pffan239

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.