@@ -42,13 +42,11 @@ For this plugin to work it's supposed that your ActionController cache store con I changed the behavior in one major way. I made the memcaching of the QueryCache optional. -You need to add `_enable_memache_querycache_` to your AcitveRecord model, like so: +You need to add `enable_memache_querycache` to your AcitveRecord model, like so: -<code> - class User < ActiveRecord::Base - enable_memcache_querycache :expires_in => 10.minutes - end -</code> + class User < ActiveRecord::Base + enable_memcache_querycache :expires_in => 10.minutes + end Additionally you can indicate in what time should expire the cache. 90 minutes is the default value. @@ -56,7 +54,7 @@ The reason for this (drastic) change is two fold: - For starters, there are many tables where trying to cache the contents but expiring all caching on any insert/update/delete/drop/alter on the table causes unnecessary overhead. A sessions table is a perfect example. I also have a metrics table and a few other tables where the contents are changed _often_. By not enabling memcache on tables that I know will constantly be changing I can save quite a number of needless memcache calls (not caching the session queries saves two reads and two writes per request). - - The other reason is I don't quite trust the implications of having a persisted query cache. I want to carefully roll it out, starting with just the few models that rarely change, and go from there. I'm not worried about users seeing information they shouldn't be, as the key is the query; it is more about making sure things expire correctly. I didn't want to push such a large caching change into my app without a careful (and long) rollout. + - The other reason is I don't quite trust the implications of having a persisted query cache. I want to carefully roll it out, starting with just the few models that rarely change, and go from there. I'm not worried about users seeing information they shouldn't be, as the key is the query; it is more about making sure things expire correctly. I didn't want to push such a large caching change into my app without a careful (and long) rollout. ## Known issues @@ -76,7 +74,7 @@ Any comments and suggestions are welcome. It's so easy to adapt the plugin for Rails version 2.0.2 if you change the cache variable for another instantiated with the memcache-client. -Also, it is possible to run in Rails >= 1.2.4 if you change the plugin [query_cache](http://agilewebdevelopment.com/plugins/query_cache) with the changes of query_memcached. +Also, it is possible to run in Rails >= 1.2.4 if you change the plugin [query\_cache](http://agilewebdevelopment.com/plugins/query_cache) with the changes of query_memcached. ## Special Thanks README.markdown 2216f30039351185667fa71e2641ca8b8c5bf973 Fernando Blat Peris ferblape@gmail.com http://github.com/ferblape/query_memcached/commit/25848ad28bd7267601ace9d0c54b2bcb80762ef5 25848ad28bd7267601ace9d0c54b2bcb80762ef5 2009-06-14T04:00:45-07:00 2009-06-14T04:00:45-07:00 Bad markdown syntax d7da8c4829dd2859b11bc7facac0dc31db88d43d Fernando Blat Peris ferblape@gmail.com