Bug #1013 configure query cache per database and/or table
Submitted: 8 Aug 2003 0:11 Modified: 8 Aug 2003 1:03
Reporter: thomas herzog Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S4 (Feature request)
Version: OS:
Assigned to: CPU Architecture:Any
Triage: D5 (Feature request)

[8 Aug 2003 0:11] thomas herzog
Description:
if mysql is use for different websites, query cache is not always the best choice.
but you can only take it ON or OFF for the complete mysql-server, or edit the entire sql-statements--> that is not always possible --> big crm's or boards.
the only way out is to use different server, to separate the different needs.

i think a config like replication(replicate-wild-ignore-table or replicate-do-db...) is a good way, to handle the different needs.

How to repeat:
use it
[8 Aug 2003 1:03] Oleksandr Byelkin
it is possible to filter some queries dependent on database, but it bring some 
overhead on _EVERY_ SELECT operation, also it will not have influence on 
fetching from query cache (we make it before parsing). 
 
More good decision will be switch off query cache by default and switch it on 
on per-connection basis. I.e. you will need to change only connecting 
procedure, but save SQL statements as is. (I mean query_cache_type variable)