#25230: Change to Query.get_count() causes big performance hit
-------------------------------------+-------------------------------------
Reporter: dexity | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 1.8
(models, ORM) |
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 akaariai):
I'm not against fixing this. We could in general remove distinct from
queries when we can prove it is redundant.
But, I don't think this is that high priority issue. I probably will get
to fixing this at some point, and I'm definitely willing to review
patches.
--
Ticket URL: <https://code.djangoproject.com/ticket/25230#comment:9>
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/064.224744cd7c1dc2c58678d3d6e77457bd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
