Jonathan wrote:
>
> I ran into the same issue. I found a cheap workaround-
>
> I have a config handle. Same db, with a readonly user called
> REGULARNAME_config , connects on prefork to pull in server config info.
>
> no matter what i do though, i can't seem to kill the config
> connection. it just kinda sits there and apache::dbi won't clear it.
> annoying.
It's because Apache::DBI overrides disconnect() to make it a no-op. If you are
connecting during your apache startup phase then you shouldn't use Apache::DBI.
You can turn it off, connect to the database and then turn it back on with
something like:
use Apache::DBI;
use DBI:
BEGIN{ $DBI::connect_via = 'connect_cached'; };
# do your stuff
$dbh->disconnect();
$DBI::connect_via = 'Apache::DBI::connect';
--
Michael Peters
Developer
Plus Three, LP
