there shouldn't be any issues with keeping a dbh in a modules' namespace for re-use by any methods in that module
Yes there should. Don't do that unless you're prepared to handle all the contingencies. Nearly everyone should be able to use Apache::DBI or DBI->connect_cached. If you need help with those, please ask.

What's the strange behavior you see when you fork? Just anomalies in your time logs, or something else?

One thing to watch out for is that many databases will call server-side cleanup routines when a dbh is closed or times out. You can control this with InactiveDestroy. You also typically need to open a new connection in the child, so if you're trying to keep using a connection opened in the parent, try making a new one instead.


In reply to Re: mod_perl, dbh, forked by perrin
in thread mod_perl, dbh, forked by Cagao

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.