On Jan 15, 2007, at 3:04 PM, John ORourke wrote:
The thought process I've gone through corroborates this - at the
most complex point I was looking at specifying a caching policy for
each table - eg. (in a shop website) product info except stock
levels can be cached for a day, static pages
Perrin Harkins wrote:
On Mon, 2007-01-15 at 13:02 -0600, Frank Wiles wrote:
Not being a MySQL guy this could be fixed now, but last I heard
MySQL tossed it's cache anytime the table was updated. Not very
efficient IMHO.
Yes, modifying data in a table invalidates the cache fo
On Mon, 2007-01-15 at 13:02 -0600, Frank Wiles wrote:
>Not being a MySQL guy this could be fixed now, but last I heard
>MySQL tossed it's cache anytime the table was updated. Not very
>efficient IMHO.
Yes, modifying data in a table invalidates the cache for that table.
There's really
On Mon, 15 Jan 2007 11:38:34 -0500
Perrin Harkins <[EMAIL PROTECTED]> wrote:
> > - if MySQL's cache is very efficient, should I bother caching in
> > my own code?
Not being a MySQL guy this could be fixed now, but last I heard
MySQL tossed it's cache anytime the table was updated. Not ver
On Mon, 2007-01-15 at 15:54 +, John ORourke wrote:
> - MySQL caches compiled statements, so why should I bother using
> prepare/execute?
Do you mean "Why should I bother using prepare_cached?" The reason for
that is the additional overhead of object creation that it avoids on the
database c
Hi folks, please humour me with this slightly OT RFC...
So I've re-invented the wheel (or MVC framework) and need to make it
efficient. A high-traffic site is using the system and is causing me
some grief...
Some questions have come up re efficient caching:
- MySQL caches compiled statement
