perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Enno <burg...@xs4all.nl>
Subject Re: Database transaction across multiple web requests
Date Fri, 31 Mar 2006 14:38:47 GMT


On Fri, 31 Mar 2006, Perrin Harkins wrote:

> Jeff wrote:
> > Your application simply uses approach (b) and MySQL does the rest
> > automatically. So if you
> >
> >   SELECT * FROM mytable WHERE something='complex' LIMIT 0,30;
> >
> > and then on another page / connection:
> >
> >   SELECT * FROM mytable WHERE something='complex' LIMIT 30,30;
> >
> > and then...
> >
> >   SELECT * FROM mytable WHERE something='complex' LIMIT 60,30;
> >
> > The main hit is on the first query, and provided that the data is not
> > updated on the server, query 2 and query 3 are served directly from the
> > cache.
>
> Have you tried this?  I was under the impression that MySQL would just
> stop when it finds enough row to satisfy LIMIT, so it wouldn't cache the
> whole result set.
>
> - Perrin
>

MySQL's cache only works for exact query matches, including the values you
use for LIMIT.

Enno


Mime
View raw message