#33008: Document prefetch_related for GenericForeignKey - Object doesn't exist
behaviour
--------------------------------------+------------------------------------
Reporter: Martin Svoboda | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.contenttypes | Version: 3.2
Severity: Normal | Resolution:
Keywords: Documentation | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Martin Svoboda):
I updated the object fetching logic of {{{__get__}}}. It respects
{{{None}}} as value if the instance exists in the cache. Is this solution
ok? It came to me as more readable than passing different {{{None}}}
values.
https://github.com/martinsvoboda/django/commit/7c83cec8b3bb99d9fe1822c3f82e58b373338a63
#diff-76b33afd71c30afb749a0de312cfe4a4578d78abae84a9d5db06388a4b1bc454R231
--
Ticket URL: <https://code.djangoproject.com/ticket/33008#comment:9>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.a57b88aa24d6a26f361c4a8ca14d4230%40djangoproject.com.
