#10961: Allow users to override forward and reverse relationships on proxy
models
with !ForeignKey fields.
-------------------------------------+-------------------------------------
Reporter: Tai Lee | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: proxy ForeignKey | Triage Stage: Accepted
reverse relationship manager |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by powderflask):
Re: https://github.com/datamade/django-proxy-overrides
This approach seems to fail when using `.select_related('related')`, where
'related' field is defined with a proxy override.
This is counter intuitive, since `myProxyInstance.related` returns a
different type of object depending on whether the original queryset used
`.select_related` or not.
Hope its useful to document that here.
--
Ticket URL: <https://code.djangoproject.com/ticket/10961#comment:14>
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/067.34c205b1f5aa5afe402d957557a477f7%40djangoproject.com.
