Perrin Harkins wrote:
So, the question is, what's an elegant way to eliminate this warning? I
could modify Apache::DBI to do it (although filtering a specific
warning, as opposed to simply turning them all off temporarilly, could
be a pain). I could install a WARN handler. Ick. Any other brigh
e mightily useful for dev.
Assuming one connection per process, I'd just set my MaxClients to fewer
than the number of SESSIONS_PER_USER. Not exactly an Apache::DBI
solution, but if you have control over your dev environment's httpd.conf
it might could work.
-- Douglas Hunter
, and have been very happy with the results so far.
-- Douglas Hunter
