#23326: DatabaseCache must implement incr to guarantee atomic increment
-------------------------------------+--------------------
Reporter: vinayan3 | Owner: nobody
Type: Bug | Status: new
Component: Core (Cache system) | Version: 1.6
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+--------------------
django.core.cache.backends.db.DatabaseCache uses BasesCache's incr which
does a get followed by a set. If the application uses multiple servers the
increments will get clobbered. Furthermore, the current implementation
overwrites the expiry time of a key to the default value instead of using
the value which was initially set.
--
Ticket URL: <https://code.djangoproject.com/ticket/23326>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.accb3a9862204332aabfa8dab9a006bc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
