On Mon, 15 May 2000, Autarch wrote:
> On Mon, 15 May 2000, Jay Jacobs wrote:
>
> > mod_perl" and there's one thing I don't quite grok about it. Let's say I
> > have a site that goes through select statements like water. If I were to
> > cache the statement handler (as described in the guide),
On Mon, 15 May 2000, Ken Y. Clark wrote:
> On Mon, 15 May 2000, Jeffrey W. Baker wrote:
>
> > On Mon, 15 May 2000, Jay Jacobs wrote:
> >
> > > I've been reading over the guide on "Efficient Work with Databases under
> > > mod_perl" and there's one thing I don't quite grok about it. Let's say I
On Mon, 15 May 2000, Jeffrey W. Baker wrote:
> On Mon, 15 May 2000, Jay Jacobs wrote:
>
> > I've been reading over the guide on "Efficient Work with Databases under
> > mod_perl" and there's one thing I don't quite grok about it. Let's say I
> > have a site that goes through select statements l
On Mon, 15 May 2000, Jay Jacobs wrote:
> mod_perl" and there's one thing I don't quite grok about it. Let's say I
> have a site that goes through select statements like water. If I were to
> cache the statement handler (as described in the guide), how does the
> database (database dependant) ha
On Mon, 15 May 2000, Jay Jacobs wrote:
> I've been reading over the guide on "Efficient Work with Databases under
> mod_perl" and there's one thing I don't quite grok about it. Let's say I
> have a site that goes through select statements like water. If I were to
> cache the statement handler (
I've been reading over the guide on "Efficient Work with Databases under
mod_perl" and there's one thing I don't quite grok about it. Let's say I
have a site that goes through select statements like water. If I were to
cache the statement handler (as described in the guide), how does the
databas
