- Fixes an invalidation issue that could rarely occur when querying on a
BinaryField
with PostgreSQL, or with some geographic queries (there was a small chance that a same query with different parameters could erroneously give the same result as the previous one) - Adds a
CACHALOT_UNCACHABLE_TABLES
setting - Fixes a Django 1.7 migrations invalidation issue in tests
(that was leading to this error half of the time:
RuntimeError: Error creating new content types. Please make sure contenttypes is migrated before trying to migrate apps individually.
) - Optimises tests when using django-cachalot by avoid several useless cache invalidations
- Fixes an
AttributeError
occurring when excluding through a many-to-many relation on a child model (using multi-table inheritance) - Stops caching queries with random subqueries – for example
User.objects.filter(pk__in=User.objects.order_by('?'))
- Optimises automatic invalidation
- Adds a note about clock synchronisation
- Fixes an invalidation issue discovered by Helen Warren that was occurring
when updating a
ManyToManyField
after executing using.exclude
on that relation. For example,Permission.objects.all().delete()
was not invalidatingUser.objects.exclude(user_permissions=None)
- Fixes a
UnicodeDecodeError
introduced with python-memcached 1.54 - Adds a
post_invalidation
signal
Fixes a bug occurring when caching a SQL query using a non-ascii table name.
Added:
- Adds an invalidate_cachalot command to invalidate django-cachalot from a script without having to clear the whole cache
- Adds the benchmark introduction, conditions & results to the documentation
- Adds a short guide on how to configure Redis as a LRU cache
Fixed:
Fixes a rare invalidation issue occurring when updating a many-to-many table after executing a queryset generating a
HAVING
SQL statement – for example,User.objects.first().user_permissions.add(Permission.objects.first())
was not invalidatingUser.objects.annotate(n=Count('user_permissions')).filter(n__gte=1)
Fixes an even rarer invalidation issue occurring when updating a many-to-many table after executing a queryset filtering nested subqueries by another subquery through that many-to-many table – for example:
User.objects.filter( pk__in=User.objects.filter( pk__in=User.objects.filter( user_permissions__in=Permission.objects.all())))
Avoids setting useless cache keys by using table names instead of Django-generated table alias
Added:
- Caches all queries implying
Queryset.extra
- Invalidates raw queries
- Adds a simple API containing:
invalidate_tables
,invalidate_models
,invalidate_all
- Adds file-based cache support for Django 1.7
- Adds a setting to choose if random queries must be cached
- Adds 2 settings to customize how cache keys are generated
- Adds a django-debug-toolbar panel
- Adds a benchmark
Fixed:
- Rewrites invalidation for a better speed & memory performance
- Fixes a stale cache issue occurring when an invalidation is done exactly during a SQL request on the invalidated table(s)
- Fixes a stale cache issue occurring after concurrent transactions
- Uses an infinite timeout
Removed:
- Simplifies
cachalot_settings
and forbids its use or modification
- Fixes an issue with pip if Django is not yet installed
- Adds multi-database support
- Adds invalidation when altering the DB schema using migrate, syncdb, flush, loaddata commands (also invalidates South, if you use it)
- Small optimizations & simplifications
- Adds several tests
- Adds thread-safety
- Optimizes the amount of cache queries during transaction
- Adds memcached support
- Adds
CACHALOT_ENABLED
&CACHALOT_CACHE
settings - Allows settings to be dynamically overridden using
cachalot_settings
- Adds some missing tests
- Fixes
pip install
.
- Adds Travis CI and adds compatibility for:
- Django 1.6 & 1.7
- Python 2.6, 2.7, 3.2, 3.3, & 3.4
- locmem & Redis
- SQLite, PostgreSQL, MySQL
- Handles transactions
- Adds lots of tests for complex cases
- Adds a test suite
- Fixes invalidation for data creation/deletion
- Stops caching on queries defining
select
orwhere
arguments withQuerySet.extra
Prototype simply caching all SQL queries reading the database and trying to invalidate them when SQL queries modify the database.
Has issues invalidating deletions and creations.
Also caches QuerySet.extra
queries but can’t reliably invalidate them.
No transaction support, no test, no multi-database support, etc.