Debuggers are nice, but they aren't always the solution. What usually works for me is to take stuff out until the bug goes away. Then you know where it is and you can make a tiny example and post it here.

Locking can be very dangerous with Apache::DBI. If you lock tables, make sure you add cleanup handlers that unlock them. Otherwise, your code could die in the middle and leave a table locked.

Something that often helps with "random" bugs is to run in -X mode so that you hit the same process each time. Also, as I mentioned in your other post, try using TCP instead of local sockets. I know it's voodoo, but more people run it that way so it has been better debugged.

In reply to Re: mysql, locked databases, Apache::DBI and mod_perl by perrin
in thread mysql, locked databases, Apache::DBI and mod_perl by Flame

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.