#27536: order_by('pk') is not obeyed if superclass has default ordering
-------------------------------------+-------------------------------------
Reporter: Andrew Dodd | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: order_by ordering | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => duplicate
Comment:
Hi Andrew,
Thanks for your detailed report.
While confusing ordering by a foreign key relies on the referenced model
`_meta.ordering` if defined. In the case of MTI a `OneToOneField` to the
parent is used as a primary key which makes ordering by `pk` follows the
`pk` -> `parent_ptr` -> `Parent._meta.ordering` chain.
See #26195 resolution for more details.
--
Ticket URL: <https://code.djangoproject.com/ticket/27536#comment:2>
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/068.0b2ea92878ff55509068cea56f454321%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.