On Sep 20, 2007, at 23:42, K J wrote:
I suppose the main problem is this... If I wanted to store the
entire list, I would have to fetch the entire dataset from the DB,
whereas if I were doing it via SQL queries, I would use paging.
Does this mean that I would, the first time a user logs in and
interacts with this list, to fetch the entire set instead of say
just page 1, then use the entire set when doing paging and other
organizing?
You can do it in whatever way makes the most sense to you.
Memcached should always be faster than the DB, and it's *much* easier
to scale. A cache miss means you have to do another request to get
more data, and then do a cache set. Otherwise, just imagine how you
want something to work, think about this layer being cheap, and start
experimenting.
--
Dustin Sallings
