The query_cache TimeToLive is variable. The query will be in the
cache as long as the data does not change. Once a table/data changes,
the query cache for those tables are cleared. It's not the best
implementation, but it's way better than nothing.
MySQL 5 does have an "on demand" query cache setting. This allows you
to specific which queries should be cached. This is generally useful
when most of your tables change constantly (making a cache useless),
but a few tables do not. The setting is one of the variables you can
set (SHOW VARIABLES) to either 0, 1, or 2 as I recall.
The Falcon engine (MySQL 6) actually has a very good caching
mechanism, but that's not officially released yet.
Brent
On Jan 8, 2008, at 11:20 AM, Thomas Raso wrote:
Hi all,
how mysql manage the query_cache TimeToLive (live) and how can I
change it ?
Thanks
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
