Continuing from... http://code.djangoproject.com/ticket/14492
> the real issue here is "What is a Proxy", and "what is equality"
I agree, that is the real issue. I based most of my reasoning off of
what the docs already state in that a proxy model can be written to
extend the behavior of the model being proxied, i.e. the data model
cannot be changed. That being said, I feel the default behavior when
dealing with equality, other data related things... should inherit
from there parent. If there is a need to override this behavior, I am
sure other hooks can be implemented to customize proxy models
differently then there parent. With regards to my primary issue of
equality, in this context two objects are being compared to determine
whether they represent the same row of data. It seems less likely to
compare two model objects to only be interested in whether they are
equal data structures.
Regarding permissions, the arguments presented in http://code.djangoproject.com/ticket/11154
all can be accomplished with writing a custom manager for the proxy
model or writing a custom ModelAdmin class for the admin. I agree with
Malcolm that a proxy model's permission should shadow its parent.
On Oct 19, 9:08 am, Byron <bjr...@gmail.com> wrote: