> From: John Gibbons [mailto:[EMAIL PROTECTED]
> Subject: Re: Is there a point in using the request object for
> db connectionswhenusing Apache::DBI?
>
> >Most of the modules that I write for such applications inherit from a
> >common base database class (think home grown Class::DBI) and have
>
> > From: John P. Gibbons [mailto:[EMAIL PROTECTED]
> > Subject: Is there a point in using the request object for db
> > connections when using Apache::DBI?
>
> Hi John,
>
> (note - I use HTML::Embperl extensively and exclusively so my ideas
> may be slanted somewhat)
That should read HTML::
Hi,
>
> What's more, is this the appropriate place for these sorts of
> questions?
I think the list is an appropriate place for such a discussion.
Even better would be if the results of such a discussion, becomes a HOWTO or
something similar.
The Embperl web site has the possibility to add thin
Most of the modules that I write for such applications inherit from a
common base database class (think home grown Class::DBI) and have
intrinsic class-based handle sharing but its all the same idea.
None of the website code cares about database details whatsoever.
Abstraction and website code sim
On Tue, 13 Jul 2004 15:07:30 -0700, John P. Gibbons <[EMAIL PROTECTED]>
wrote:
I was reading this article:
http://www.perl.com/pub/a/2001/03/embperl.html and of course this
mailing list and have seen reference to people using the $req object to
have one database connection.
On my sites I did
