#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 David Sanders):
Just FYI re:
{{{
django.db.utils.DatabaseError: ORDER BY not allowed in subqueries of
compound statements.
}}}
SQLite doesn't support limits & ordering in compound statments:
https://www.sqlite.org/lang_select.html#compound_select_statements
The error we're seeing here is a Django feature flag checking the presence
of an order by. The `Author` model in the test has a default `ordering`
which is causing this.
--
Ticket URL: <https://code.djangoproject.com/ticket/34123#comment:7>
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/010701842eec4f43-ff2a0804-ba15-4fb2-beb8-983241d53347-000000%40eu-central-1.amazonses.com.
