django-cachalot/CHANGELOG.rst
Bertrand Bordage 9d2aba8680 Version 1.0.1.
2015-04-17 20:44:39 +02:00

151 lines
3.9 KiB
ReStructuredText
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Whats new in django-cachalot?
==============================
1.0.1
-----
- 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
invalidating ``User.objects.exclude(user_permissions=None)``
- Fixes a ``UnicodeDecodeError`` introduced with python-memcached 1.54
- Adds a ``post_invalidation`` signal
1.0.0
-----
Fixes a bug occurring when caching a SQL query using a non-ascii table name.
1.0.0rc
-------
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 invalidating
``User.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
0.9.0
-----
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
0.8.1
-----
- Fixes an issue with pip if Django is not yet installed
0.8.0
-----
- 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
0.7.0
-----
- Adds thread-safety
- Optimizes the amount of cache queries during transaction
0.6.0
-----
- Adds memcached support
0.5.0
-----
- Adds ``CACHALOT_ENABLED`` & ``CACHALOT_CACHE`` settings
- Allows settings to be dynamically overridden using ``cachalot_settings``
- Adds some missing tests
0.4.1
-----
- Fixes ``pip install``.
0.4.0 (**install broken**)
--------------------------
- 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
0.3.0
-----
- Handles transactions
- Adds lots of tests for complex cases
0.2.0
-----
- Adds a test suite
- Fixes invalidation for data creation/deletion
- Stops caching on queries defining ``select`` or ``where`` arguments
with ``QuerySet.extra``
0.1.0
-----
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 cant reliably invalidate them.
No transaction support, no test, no multi-database support, etc.