#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: new
Component: Database layer | Version:
(models, ORM) | 1.7-beta-2
Severity: Release blocker | Resolution:
Keywords: distinct, query | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by charettes):
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/2614 Create a PR with doc and
release note]. I would appreciate a wording review.
In order to make sure the test refactoring didn't break anything I review
and moved every cases in their own methods. I you feel like this is adding
too much noise to the patch I can remove this part from the final patch.
--
Ticket URL: <https://code.djangoproject.com/ticket/19195#comment:10>
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.e73407c6ef236ed1dfda480bfb8d6851%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
