#33796: Combined queries with ordering are no longer usable as subqueries on
PostgreSQL and MySQL.
-------------------------------------+-------------------------------------
Reporter: Shai Berger | Owner: Mariusz
| Felisiak
Type: Bug | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Release blocker | Resolution: fixed
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 <felisiak.mariusz@…>):
In [changeset:"d38cd2677e4d8303e70e3bc1119deda7371b369a" d38cd267]:
{{{
#!CommitTicketReference repository=""
revision="d38cd2677e4d8303e70e3bc1119deda7371b369a"
[4.1.x] Fixed #33796 -- Fixed ordered combined queryset crash when used in
subquery on PostgreSQL and MySQL.
Thanks Shai Berger for the report.
Regression in 30a01441347d5a2146af2944b29778fa0834d4be.
Backport of 44ffd8d06fabc07d8333f31439e8dd39ea87329b from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33796#comment:4>
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/01070181a3666150-512a2acf-fed7-44cf-afaa-07db67dac986-000000%40eu-central-1.amazonses.com.
