I have an abstract base model as well several models that subclass it.
Now I am figuring out how to design the ModelAdmin subclasses for
these models.
I need a ModelAdmin that can display the fields of the base model (so
that the ModelAdmins for the child models don't have to do that
themselves) as well as perform certain operations when saving a model
that must be done by all of the child models. I've come up with a
ModelAdmin subclass that works with the abstract base model, but am
unsure how to properly subclass it for the child models.
Specifically, I'm unsure how to handle properties like fieldsets,
inlines, and list_display. These would be properties I'd set in the
base ModelAdmin to ensure that the common information provided by the
base model is available in all the models. But if I set those
properties in the ModelAdmin subclasses for the child models I would
be overriding the information set by the base model's ModelAdmin.
The best way around this is to use an append instead of an assignment
("+=" instead of "=") when configuring these properties in the child
model ModelAdmins. Would this be my best bet?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
