#36590: Redis, Memcached, and Database cache backends lack specialized many
operation implementations
--------------------------------------+------------------------------------
Reporter: Brian Atkinson | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Core (Cache system) | Version: 5.2
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
--------------------------------------+------------------------------------
Changes (by Simon Charette):
* component: Uncategorized => Core (Cache system)
* stage: Unreviewed => Accepted
* summary: Redis cache lacks specialized aget_many and aset_many
implementations =>
Redis, Memcached, and Database cache backends lack specialized many
operation implementations
* type: Uncategorized => Cleanup/optimization
Comment:
Memcached and database backends are also affected as well as `delete_many`
I wonder if we could potentially have
`BaseDatabaseCache.__init_subclass__` automatically add specialized
`aget_many`, `aset_many`, `adelete_many` when one is declared by a
subclass.
--
Ticket URL: <https://code.djangoproject.com/ticket/36590#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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701990cc104f1-e716d084-348a-4a2d-8b0e-3dc5c8ed720d-000000%40eu-central-1.amazonses.com.
