#32116: QuerySet.order_by() crashes on combined queryset with a single non-empty
query.
-------------------------------------+-------------------------------------
Reporter: Hannes Ljungberg | Owner: hannes
| ljungberg
Type: Bug | Status: assigned
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Raising `django.db.utils.DatabaseError: ORDER BY not allowed in subqueries
of compound statements.` is not a big issue IMO, I would say that is a
cleanup. However it generates and incorrect SQL after
2cbd3967e0a51eab993df89679046d25ec78baec which should be fixed as a bug.
--
Ticket URL: <https://code.djangoproject.com/ticket/32116#comment:5>
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/067.d2bca48eb7aae6aa094fdff5548b2c9b%40djangoproject.com.
