Howdy!

Putting in adequate error checking is part and parcel of getting the general function working. If your code can't tell if the database actions worked or not, it's broken. At the least, you can't demonstrate that it isn't broken.

You could try setting RaiseError to true, which will make it blow up when a DBI error occurs. That will be better than nothing, especially if you couple that with CGI::FatalsToBrowser (or whatever that bit is that makes the CGI error messages go to the browser instead of the local error log where you might never see them.

yours,
Michael

In reply to Re^3: Database access on your site, or "Where the hell is mysql?" by herveus
in thread Database access on your site, or "Where the hell is mysql?" by SkipHuffman

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.