#26815: Addition of Trunc may have altered the ordering of dates() queries
----------------------------------------------+----------------------------
Reporter: Kazade | Owner: nobody
Type: Bug | Status: new
Component: Database layer (models, ORM) | Version: 1.10
Severity: Normal | Keywords: dates,
| queryset
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+----------------------------
We're looking into supporting Django 1.10 in Djangae, and while fixing up
some breakages I noticed a change in the way that dates() queries are
ordered. I'm not 100% sure this is a real bug as I'm looking at the code
in a fairly abnormal situation, but it definitely seems like a bug...
This line was recently added as part of the datetime expression changes:
https://github.com/django/django/commit/2a4af0ea43512370764303d35bc5309f8abce666
#diff-5b0dda5eb9a242c15879dc9cd2121379R743
It seems to me that now, instead of ordering by the full date, this change
will make dates queries order by just the component that they are
selecting (e.g. year, month, day etc.) - although I might be wrong about
this!
--
Ticket URL: <https://code.djangoproject.com/ticket/26815>
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/049.9a2df3894331600d0177306e76efa5b9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
