#27594: Reverse one to one related object populated from incorrect query columns
-------------------------------------+-------------------------------------
Reporter: Daniel Hillier | Owner: Daniel
| Hillier
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: onetoone reverse | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"7da37699e8d7124f5d0cfaba931772333c24ef83" 7da37699]:
{{{
#!CommitTicketReference repository=""
revision="7da37699e8d7124f5d0cfaba931772333c24ef83"
Fixed #27594 -- Fixed select_related() with reverse self-referential
OneToOneField.
Fixed definition of `klass_info['from_parent']` so that two models aren't
considered from a parent class if the model classes are the same.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27594#comment:5>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.ed0a6f242e0eb334257237ca90101947%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
