#15054: ContentTypes and proxied models
-----------------------------------+----------------------------------------
Reporter: jakedrake | Owner: nobody
Status: closed | Milestone:
Component: Contrib apps | Version: 1.2
Resolution: duplicate | Keywords: contentype proxy
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------+----------------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => duplicate
Comment:
I'm going to mark this one a duplicate. It isn't exactly the same
presentation as #14492 or #11154, but the root cause is the same -- an
inconsistency with the understanding of whether a proxy model is the same
content type or a different content type. Having another open ticket
doesn't help clarify the underlying problem.
I'm loathed to introduce a new meta setting like you describe, but given
the widespread usage of Proxy classes (and the conflict in understanding
what it means), it may be the only way to resolve the problem.#
--
Ticket URL: <http://code.djangoproject.com/ticket/15054#comment:3>
Django <http://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.
