Django-cacheops

Latest version: v7.0.2

Safety actively analyzes 619599 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 10

7.0.2

- fixed .aggregate()
- fixed big memory usage during migrations
- fixed INSIDEOUT in older redises
- better handle model families with abstracts in them
- allow funcy 2.0+

7.0.1

- made it work with Redis 6.x and older again
- handle abstract models better
- some docs improvements

7.0

- support Django 4.2b and 5.0a
- added a new insideout mode
- made join invalidation more granular
Backwards incompatible changes:
- dropped Python 3.5, 3.6 and Django 2.1, 2.2, 3.0 and 3.1 support
- removed CACHEOPS_LRU
- removed CacheopsRedis, should inherit redis.Redis instead

6.2

- support Python 3.11 and Django 4.1
- added command to clear stale cacheops keys (Bruno Alla)
- fixed `invalidate_m2o` for polymorphic models (430) (Andrey Alekseev)
- updated README: TOC, link to the post, some explanations

6.1

- support Django 3.2 and 4.0 (thx to Olivér Kecskeméty)
- do not gulp commit errors (Oleg Yamnikov)
- fixed precall key when a prefix is defined (Peter Baumgartner)
- fixed m2o/m2m queries invalidation on object deletion (thx to Sergey Tikhonov)

6.0

- support and test against Python 3.9 and Django 3.1/3.2
- added custom serializers support (thx to Arcady Usov)
- support callable extra in cached_as() and friends
- made simple cache obey prefix
- skip JSONFields for purposes of invalidation
- configure skipped fields by internal types, classes still supported
- handle `DatabaseError` on transaction cleanup (Roman Gorbil)
- do not query old object if cacheops is disabled
- do not fetch deferred fields during invalidation, fixes 387
Backwards incompatible changes:
- callable `extra` param, including type, now behaves differently
- simple cache now uses prefix

Page 1 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.