John M Vinopal wrote:
> For programmer ease you probally want to connect inside a module, and for
> mod_perl speed you want to preload that module. But you can't do both AND
> connect once at the start. Mod_perl insists that dbh connections must not
> be made in the parent and then used in the c
Part of the problem I've had is transitioning a cgi application onto
mod_perl and keeping performance up on both platforms until a switch
can be made. So I've done some comparisons of the various dbh schemes.
Comments and corrections very welcome. I'm wary of connect_cached()
under mod_perl but
Tim Gardner wrote:
>
> I have been using DBI without Apache::DBI and have been simply
> storing db connections in a global variable as a sort of poor man's
> persistent connection when running under Apache::Registry.
>
> Now I want to do things "right" and am trying to understand
> Apache::DBI.
Tim wrote:
> Now I want to do things "right" and am trying to understand
> Apache::DBI. Before looking at the module I imagined that it would
> work by providing a library of persistent connections. You would
> check a connnection out of the library, use it, and then put it back
> when you
I have been using DBI without Apache::DBI and have been simply
storing db connections in a global variable as a sort of poor man's
persistent connection when running under Apache::Registry.
Now I want to do things "right" and am trying to understand
Apache::DBI. Before looking at the module
