#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 | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+------------------------------------
Changes (by freakboy3742):
* needs_docs: => 0
* needs_better_patch: => 0
* needs_tests: => 0
* easy: 0 => 1
* stage: Unreviewed => Accepted
Comment:
You are correct that the implementation of incr on the DB cache backend
will be subject to race conditions, so we should fix that.
However, I'd also say that if you're using the database cache backend for
a count where there is heavy traffic, You're Doing It Wrong(TM). You
should be using Redis, or at least Memcached.
--
Ticket URL: <https://code.djangoproject.com/ticket/23326#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.6b99f9514c52e91d8ee1cbab5787ac8f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
