#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
-------------------------------------+-------------------------------------
Comment (by Simon Charette <charette.s@…>):
In [changeset:"0cf85e6b074794ac91857aa097f0b3dc3e6d9468" 0cf85e6b]:
{{{
#!CommitTicketReference repository=""
revision="0cf85e6b074794ac91857aa097f0b3dc3e6d9468"
Refs #29908 -- Optimized known related objects assignment.
Since CPython implements a C level attrgetter(*attrs) it even outperforms
the
most common case of a single known related object since the resulting
attribute
values tuple is built in C.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29908#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 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/066.73aa89572994c45d9ee71a89ceb07bd9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
