#14492: Model proxy instance does not equal the respective model instance
-------------------------------------+-------------------------------------
Reporter: bruth | Owner: bruth
Status: assigned | Milestone: 1.3
Component: Database | Version: SVN
layer (models, ORM) | Keywords:
Resolution: | Has patch: 1
Triage Stage: Design | Needs tests: 0
decision needed |
Needs documentation: 0 |
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Changes (by lukeplant):
* stage: Ready for checkin => Design decision needed
Comment:
If I read those other discussions correctly, there is no consensus that
this is the correct design decision, so it cannot be 'Ready for checkin'.
The closest we have to consensus is on #15054, which has a valid use case
for proxy models **not** being treated as equal (with a loose definition
of 'equal') to the parent model, which goes the other way from this. So
I'm knocking it back to 'design decision needed'.
--
Ticket URL: <http://code.djangoproject.com/ticket/14492#comment:11>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
