#34012: QuerySet.order_by() silently skips non-existing fields on related fields
with Meta.ordering.
-------------------------------------+-------------------------------------
Reporter: Klaas van Schelven | Owner: David
Type: | Sanders
Cleanup/optimization | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"4771a1694b3b54c7309602820881d3ec9cc2c809" 4771a169]:
{{{
#!CommitTicketReference repository=""
revision="4771a1694b3b54c7309602820881d3ec9cc2c809"
Fixed #34012 -- Made QuerySet.order_by() apply transforms on related
fields for models with Meta.ordering.
This makes QuerySet.order_by() no longer ignore trailing transforms for
models with Meta.ordering. As a consequence, FieldError is raised in
such cases for non-existent fields.
Thanks to Klaas van Schelven for the report and Mariusz Felisiak for the
review and advice.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34012#comment:11>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070183a1c27a61-7b2feadf-f8dc-4775-9473-1b63bfdeb95d-000000%40eu-central-1.amazonses.com.
