there shouldn't be any issues with keeping a dbh in a modules' namespace for re-use by any methods in that moduleYes 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
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |