#33796: Combined queries with ordering are no longer usable as subqueries on PostgreSQL and MySQL. -------------------------------------+------------------------------------- Reporter: Shai Berger | Owner: nobody Type: Bug | Status: new Component: Database layer | Version: 4.1 (models, ORM) | Severity: Release blocker | Resolution: Keywords: | Triage Stage: Accepted Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by Mariusz Felisiak):
* stage: Unreviewed => Accepted Comment: Thanks for the report. I'm not sure how to fix this as it's really tricky to juggle parentheses around combined queries with different databases (see also #31445). Regression in 30a01441347d5a2146af2944b29778fa0834d4be. -- Ticket URL: <https://code.djangoproject.com/ticket/33796#comment:1> 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/0107018187b9347b-05fc24ac-84fa-4f74-8a09-7ddcda6ce22c-000000%40eu-central-1.amazonses.com.