#29340: "cache.get_or_set()" extra hits on database
-------------------------------------+-------------------------------------
Reporter: hematinik | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Core (Cache system) | Version: 2.0
Severity: Normal | Resolution:
Keywords: cache | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by hematinik):
Replying to [comment:2 Tim Graham]:
> Can you explain why Django is at fault? I haven't debugged your project
but I think it's more likely that you've made a mistake somewhere.
django is expected to use cached data and not to create sql queries when
the required cache keys are present. as I explained my information is
based on the statistics **django-debug-toolbar** provides so "maybe" it
is not the django's fault. I don't think there is any problem with the
code itself. I simplified the code for clearance but I'm sure it resembles
the situation of my project's behavior.
--
Ticket URL: <https://code.djangoproject.com/ticket/29340#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/067.117dc970a2874429b7a8f3d9e31f7283%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
