#29195: Postgres Regression, annotating Exists through a OuterRef query.
-------------------------------------+-------------------------------------
     Reporter:  Oli Warner           |                    Owner:  Simon
                                     |  Charette
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  2.0
  (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 Tim Graham <timograham@…>):

 In [changeset:"0fd21febe7b3969460e3e6f17bfedc63529f194b" 0fd21feb]:
 {{{
 #!CommitTicketReference repository=""
 revision="0fd21febe7b3969460e3e6f17bfedc63529f194b"
 [2.0.x] Fixed #29195 -- Fixed Exists.output_field resolution on single-
 valued queries.

 The Subquery class which Exists inherits from defaulted to using single-
 valued
 querie's field if no output_field was explicitly specified on
 initialization
 which was bypassing the Exists.output_field defined at the class level.

 Moving Subquery's dynamic output_field resolution to _resolve_output_field
 should make sure the fallback logic is only performed if required.

 Regression in 08654a99bbdd09049d682ae57cc94241534b29f0.

 Thanks Oli Warner for the detailed report.

 Backport of 277ed072094ad87fc6b2c4669f21d43b1f39043c from master
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/29195#comment:8>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.e2804c063c3b0c818562643896e63b01%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to