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

[Django]

#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 ):

 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: 
Django 
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/01070181a3666150-512a2acf-fed7-44cf-afaa-07db67dac986-00%40eu-central-1.amazonses.com.

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

[Django]

#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 ):

 * 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: 
Django 
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/01070181a364f251-1e2dc81f-915f-40e6-8183-eaad6f31926f-00%40eu-central-1.amazonses.com.

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

[Django]

#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: 
Django 
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/01070181943ada1a-fb0a31e1-d37b-41f4-814d-3c321c81275b-00%40eu-central-1.amazonses.com.

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

[Django]

#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: 
Django 
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-00%40eu-central-1.amazonses.com.