Django-cacheops

Latest version: v7.1

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

Scan your dependencies

Page 7 of 10

2.2.1

Not secure
- fixed thread local error
- fixed ops = 'all' both in config and .cache()

2.2

Not secure
- switched to new CACHEOPS setting style
- added CACHEOPS_DEFAULTS setting
- work as LRU cache
- cache .exists() calls in Django 1.6+
- invalidate on .bulk_create()
- added no_invalidation context manager/decorator
- documented local_get and cache_on_save
- fixed saving objects with F-expression fields (Fedor Nasyrov)
- fixed queries with Django 1.7 transforms
- fixed binary fields in python 3
- stopped using simplejson
- simpler queryset key calculation,
third party fields should be more compatible now
- removed bogus clone param from .nocache() call

2.1.1

Not secure
- fixed bug in m2m invalidation
- fixed bug with null geometry fields
- fixed unpickling objects with BinaryFields

2.1

Not secure
- support Django 1.7
- do not fetch from cache when doing .select_for_update() and similar,
but do write to cache if it's enabled
- fixed inherited models exception in admin,
multi-table models are still not really supported!
- fixed fake cacheops
- fixed deprecation warning in Django 1.6 admin

2.0

Not secure
- conditions on related models will now invalidate queryset
- m2m invalidation is much more granular
- removed requirement that timeout should not be greater than default
- lua scripting is used to save and invalidate cache, making things faster
- better invalidation for complex and custom fields
- silent stringify of unknown objects by default
- support caching django.contrib.gis queries (koodjo)
- cacheops is now thread-safe
- added a way to no-op cacheops
- added cached_view() and cached_view_as()
- pass several samples for cached_as() and cached_view_as()
- fixed working with querysets created by non-patched constructor (3 and dups)
- fixed invalidate_model() for proxy models
- fixed deepcopy(queryset) bug
- fixed possible collisions when cached functions passed complex structured arguments
- fixed StringifyError on timedelta (mpyatishev)
Backwards incompatible changes:
- filters on TextFields no longer affect invalidation
- cached_as() cache key will now depend on function arguments
- cached_as() and cached() will now depend on function line in a code,
permitting usage of lambdas and same named methods without passing extra
- cached_as() and cached() will now take timeout as first argument and extra as second.
Anyway using them as keyword arguments is recommended
- Django 1.2 no longer supported
- Redis 2.6+ is required

1.3.1

Not secure
- fixed bug with negating "some"-conditions
- fixed bug with schemes unsync when invalidating model
Backwards incompatible changes:
- reverted .cache(write_only=...) behaviour to enable caching for all ops
- .cache(timeout=...) call will enable caching for all ops

Page 7 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.