#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 shaib):
Replying to [comment:7 jarshwah]:
> Really though, distinct is very rarely useful, and is indicative of a
poorly constructed query (in sql or in django). Obviously there are useful
distinct queries, but they are the exception in my experience.
It becomes necessary if you use backreferences for FKs in your filter; SQL
is stupid and multiplies results in that case.
--
Ticket URL: <https://code.djangoproject.com/ticket/25230#comment:10>
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.a6eeb69e14302830873efa6c71e8ee4f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
