Not what you asked about, but I thought I should point out that your code may cause hard to trace memory corruption. Your DBD driver is likely XS code linking to a compiled client library, most are. Interupting code like that with a signal and then trying to call back into that code will work most of the time, until it doesn't. When it doesn't you'll get very bizarre results - crashes in unrelated areas of code for example. The reason is that your DBD driver may be keeping global state which is left in an inconsistent state by your alarm interupt.

I wrote DBIx::Timeout to deal with this problem. It only works for MySQL at the moment but I believe the concept should be portable.

-sam

In reply to Re: $@ alternative by samtregar
in thread $@ alternative by Gangabass

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.