Re: Class::DBI::Factory and Apache::DBI don't play nice

[prev] [thread] [next] [Date index for 2004/11/19]

On Fri, 2004-11-19 at 17:35, Alexander Gräfe wrote:
> From what I could gather from reading the list archives, this happens if
> the db handle sticks around in a closure and doesn't go out of scope.
> Could it be HTML::Mason that interferes, since Mason uses some kind of
> compilation and caching?

Not likely, since you aren't defining subs inside your Mason
components.  Ima::DBI actually uses closures on purpose, which does sort
of wreak havoc with certain aspects of Apache::DBI, but is totally
different from the problem you're describing.  I don't know anything
about Class::DBI::Factory, but I would suggest first upgrading your
Ima::DBI and Class::DBI to the latest if they are not already there.

> What's the best way to debug such a situation?

There are several tools you can use, like DBI->trace or Apache::DB.  I
suggest running your server in -X mode so you'll get the same process on
each request, and then using the debugger or shoving warn statements
into Class::DBI::Factory.

- Perrin