I didn't run it under ModPerl::Registry, is there any risk to use the module? maybe I have to run lots of testing to the existing scripts.
Could I just run use the previous connections via DBI->connect_cache instead of the Apache::DBI in one single cgi script(but the script will call other modules which may make new db connections with same db password and attributes)? In my testing, I saw some different database handlers returned instead of the same hash reference address. On 7/30/07, Clinton Gormley <[EMAIL PROTECTED]> wrote: > On Mon, 2007-07-30 at 18:21 +0800, Ken Perl wrote: > > I've configured the Apache::DBI in httpd.conf like this, > > > > PerlModule Apache::DBI > > > > I didn't have Apache::DBI->connect_on_init($data_source, $username, > > $auth, \%attr) in startup.pl since we don't use startup.pl. and the > > doc says to config it in httpd.conf is OK. > > > > my question is I can not find any persistent connections for my CGI > > script. any usage error here? > > Persistent connections will not work for straight CGI scripts, because > CGI is not persistent. > > For each CGI request, a new perl interpreter is loaded, your script is > compiled, run, and the Perl process exits. > > mod_perl IS persistent, as are your CGI scripts run via > ModPerl::Registry etc. > > You don't need connect_on_init to work, but you do need mod_perl > > Clint > > > > -- perl -e 'print unpack(u,"62V5N\"FME;G\!E<FQ`9VUA:6PN8V]M\"[EMAIL PROTECTED] ")'
