#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
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"01b3dc22324bca66bf5d34229b03b710945077fd" 01b3dc22]:
{{{
#!CommitTicketReference repository=""
revision="01b3dc22324bca66bf5d34229b03b710945077fd"
[1.8.x] Reverted "Fixed #27594 -- Fixed select_related() with reverse
self-referential OneToOneField."
This reverts commit 4a9f9cc521f09c60f56024eb6688e30ab86b998f. It was
accidentally pushed to this branch.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27594#comment:7>
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.689d07f2087be1ab34de1c23b7cab954%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
