On Thu, Jan 16, 2003 at 04:40:07PM -0600, Christopher L. Everett wrote: > > But again, there is the issue of mapping changed data onto dependent > pages. I guess one way to do that is to track which database rows > appear in which pages in the database. Since typically I do several > database operations to generate a page, adding one more delete or > insert operation whanever a new page is generated won't kill me. > Could get nasty in a big hurry if I'm not careful though. Perhaps > a cache manager object/class that handles cache mappings & invalidation > would be handy. Or maybe do that as part the PageKit base Model class.
It all depends on the ration between updates and selects, and the number of distincts selects. New versions of MySQL have support (by default, it is disabled, I believe) for caching the results of selects. So if the ratio is good, you might just use the MySQL cache and be done with it. Of course, if your select set is so wide that it is not reasonably cachable, you are out of luck with this route. Yours, -- ------------------------------------------------------------------------ Honza Pazdziora | [EMAIL PROTECTED] | http://www.fi.muni.cz/~adelton/ ... all of these signs saying sorry but we're closed ... ------------------------------------------------------------------------
