#8444: Model inheritance - inherited model could use some fields cleanup
-------------------------------------+--------------------------------------
Reporter: trebor74hr | Owner: nobody
Status: closed | Milestone:
Component: Core framework | Version: SVN
Resolution: invalid | Keywords: model inheritance
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Comment (by Daniel Pope <[EMAIL PROTECTED]>):
Oh, well I'm a moron then. I didn't realise we had multiple inheritance.
However the first answer is as valid as yours: we have "leakage", as you
put it, because the subclass is also an instance of the superclass.
Deleting the attributes is not just impractical. It would be undesirable
if {{{isinstance(foo, Question)}}} but {{{foo.webquestion}}} raised
{{{AttributeError}}} rather than the expected
{{{WebQuestion.DoesNotExist}}}.
--
Ticket URL: <http://code.djangoproject.com/ticket/8444#comment:3>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
