#29908: Foreign key isn't set on object after related set access if ForeignKey
uses
to_field
-------------------------------------+-------------------------------------
Reporter: Carsten Fuchs | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | 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 Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"75dfa92a05c7161edd0ba7bc9ceab9b54d3383db" 75dfa92a]:
{{{
#!CommitTicketReference repository=""
revision="75dfa92a05c7161edd0ba7bc9ceab9b54d3383db"
Fixed #29908 -- Fixed setting of foreign key after related set access if
ForeignKey uses to_field.
Adjusted known related objects handling of target fields which relies on
from and to_fields and has the side effect of fixing a bug bug causing
N+1 queries when using reverse foreign objects.
Thanks Carsten Fuchs for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29908#comment:6>
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/066.10427aa235ab19259181ccdf4a7f71f2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
