#19195: Using distinct([*fields]) filter on a foreign key produces an ordering
error when the foreign key has a Meta ordering field.
-------------------------------------+-------------------------------------
Reporter: chrisedgemon@… | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version:
(models, ORM) | 1.7-beta-2
Severity: Release blocker | Resolution: fixed
Keywords: distinct, query | Triage Stage: Ready for
Has patch: 1 | checkin
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette <charette.s@…>):
In [changeset:"d773a08b270e3b2c387985a9d9a4d01c991469c8"]:
{{{
#!CommitTicketReference repository=""
revision="d773a08b270e3b2c387985a9d9a4d01c991469c8"
[1.7.x] Fixed #22711 -- Adjusted ordering checks to allow implicit
relation fields.
refs #19195.
Backport of d04e730224 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/19195#comment:18>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/080.2b54e666b8b83a33c78b1617d9cb8aeb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
