Re: [Django] #33796: Combined queries with ordering are no longer usable as subqueries on PostgreSQL and MySQL.

1 view
Skip to first unread message

Django

unread,
Jun 24, 2022, 1:41:37 AM6/24/22
to django-...@googlegroups.com
#33796: Combined queries with ordering are no longer usable as subqueries on
PostgreSQL and MySQL.
-------------------------------------+-------------------------------------
Reporter: Shai Berger | Owner: Mariusz
| Felisiak
Type: Bug | Status: assigned
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):

* owner: nobody => Mariusz Felisiak
* status: new => assigned
* has_patch: 0 => 1


Comment:

[https://github.com/django/django/pull/15793 PR]

--
Ticket URL: <https://code.djangoproject.com/ticket/33796#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jun 27, 2022, 12:21:54 AM6/27/22
to django-...@googlegroups.com
#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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):

* status: assigned => closed
* resolution: => fixed


Comment:

In [changeset:"44ffd8d06fabc07d8333f31439e8dd39ea87329b" 44ffd8d0]:
{{{
#!CommitTicketReference repository=""
revision="44ffd8d06fabc07d8333f31439e8dd39ea87329b"
Fixed #33796 -- Fixed ordered combined queryset crash when used in
subquery on PostgreSQL and MySQL.

Thanks Shai Berger for the report.

Regression in 30a01441347d5a2146af2944b29778fa0834d4be.
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/33796#comment:3>

Django

unread,
Jun 27, 2022, 12:23:28 AM6/27/22
to django-...@googlegroups.com
#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>

Reply all
Reply to author
Forward
0 new messages