On Sat, 2006-01-28 at 21:24 -0500, Michael Peters wrote:
>
> Jonathan wrote:
> >
> ]> 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
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
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 an
> Any reason why this is bad?
I've found one - only works if you use PerlRequire.
PerlPostConfigRequire happens too late in the process.
So instead, I've just forced childinit() to be called whether or not you
use connect_on_init and reset the cache there.
So in MP2, connect_on_init becomes a n
Some of my perl modules connect to the database during startup, and I
have been getting errors when my children try to connect to the
database, because they end up trying to share the $dbh handles from the
parent.
The current code that tries to prevent handle caching (according to the
comments) do
