Commits

Tobias McNulty committed b82f212

use "default" as default cache key rather than "ALL"

  • Participants
  • Parent commits 7019c7d
  • Branches issue-55

Comments (0)

Files changed (2)

File docs/queryset_cache.rst

 otherwise not invalidate a query cached for that slave when a write occurs
 on the master.  For example, if you have a simple database setup with one
 master and one slave, you could set both databases to use the database key
-``ALL`` when constructing cache keys like so::
+``default`` when constructing cache keys like so::
 
     DATABASES = {
         # ...
         'default': {
             # ...
-            'JOHNNY_CACHE_KEY': 'ALL',
+            'JOHNNY_CACHE_KEY': 'default',
         },
         'slave': {
             # ...
-            'JOHNNY_CACHE_KEY': 'ALL',
+            'JOHNNY_CACHE_KEY': 'default',
         },
     }
 

File johnny/tests/cache.py

         self.failUnless("second" in getattr(settings, "DATABASES"))
 
         old_cache_keys = johnny_settings.DB_CACHE_KEYS
-        johnny_settings.DB_CACHE_KEYS = {'default': 'ALL', 'second': 'ALL'}
+        johnny_settings.DB_CACHE_KEYS = {'default': 'default', 'second': 'default'}
 
         g1 = Genre.objects.using("default").get(pk=1)
         g1.title = "A default database"