#17648: Allow `ContentTypeManager` and `GenericForeignKey` to retreive/store
proxy
model content type.
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: charettes
Type: Bug | Status: new
Component: | Version: master
contrib.contenttypes | Resolution:
Severity: Normal | Triage Stage: Design
Keywords: contenttype proxy | decision needed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by akaariai):
While writing the django-developers post (which I never sent) I realized
this change is going to be pretty bad from backwards compatibility
perspective. Consider for example change log style usage: suddenly changes
done through proxy models will no longer register to the base model, but
to all the different proxy models used. This is a pretty bad violation of
backwards compatibility (I think admin log would show this issue for
example).
So, I suggest to split this patch to two:
1. Fix the deferred model handling
2. Add a kwarg 'for_base_model' or somesuch, defaults to 1.4 behavior,
but you can request the proxy model contenttype if you wish.
--
Ticket URL: <https://code.djangoproject.com/ticket/17648#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
