#34123: Ambiguous aliases in ordering on combined queries with select_related().
-------------------------------------+-------------------------------------
Reporter: Shai Berger | Owner: David
| Sanders
Type: Bug | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: select_related | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
I figured the origin of the `1st ORDER BY term does not match any column
in the result set` error; it's another regression introduced by
c58a8acd413ccc992dd30afd98ed900897e1f719 but solely on 3.28 and 3.29 which
should be fixed by [https://github.com/django/django/pull/16244 this PR].
The `select_related` issue remains though. Any help required David?
--
Ticket URL: <https://code.djangoproject.com/ticket/34123#comment:8>
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/0107018430ee5e36-29e7587d-00a9-499c-a0bf-4785a66e8a85-000000%40eu-central-1.amazonses.com.
