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

Reply via email to