#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: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Comment (by vinayan3):
I am not doing it wrong necessarily because our DB is very small with a
limited number of users. The table should basically live in InnoDB's
buffer pool. It's not unreasonable to just use the DB as a cache for
values.
--
Ticket URL: <https://code.djangoproject.com/ticket/23326#comment:3>
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/066.8f10ded96978967a1e0df95a5145f527%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
