#25470: Serious performance impact (500x slower!) when querying distinct model
dates objects
-------------------------------------+-------------------------------------
Reporter: stanleyxu2005 | Owner: felixxm
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"0f6d51e6a0a22e37e45c4bf452ddb49723e2f956" 0f6d51e6]:
{{{
#!CommitTicketReference repository=""
revision="0f6d51e6a0a22e37e45c4bf452ddb49723e2f956"
Fixed #25470 -- Avoided unnecessary, expensive DATETIME typecast on MySQL.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25470#comment:19>
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/071.919302ac82db78f545fb63fe36831768%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
