#23791: Subqueries with non-"id" OneToOneField primary keys try to join against 
the
wrong column name
-------------------------------------+-------------------------------------
     Reporter:  ris                  |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  1.7
  (models, ORM)                      |               Resolution:
     Severity:  Normal               |             Triage Stage:
     Keywords:  orm primary_key      |  Unreviewed
  OneToOneField subquery values      |      Needs documentation:  0
    Has patch:  0                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by ris):

 Having said the workaround behaves correctly, I realize adding .values
 (...) screws up the ordering of the subquery, which is important if using
 .distinct (...). Similar effects to #23622

--
Ticket URL: <https://code.djangoproject.com/ticket/23791#comment:2>
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/061.9cc334473f008b5217399e084f6e56a2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to