Also, I read about issues of database handlers becoming
unstable across forks. So should I place this initialization
information into a perl child init handler?
See the connect_on_init() method in the Apache::DBI docs.
We use PerlSetVar's for this where I work.
That's how I would do it
Hi! I had a question regarding where I should be placing global configuration options
in mod_perl. Here's the qweekie scenario:
I want to load a configuration file of various options (such as db arguments, system
directories, db connections, etc.) into a hash or perl object global to Apache
On Sun, 31 Mar 2002 12:43:45 -0800 (PST) [EMAIL PROTECTED] wrote:
Hi! I had a question regarding where I should be placing global
configuration options in mod_perl. Here's the qweekie scenario:
I want to load a configuration file of various options (such as db
arguments, system
