> Purely in terms of OO design, because it's cleaner. Object > composition is usually a more appropriate paradigm than class > inheritance. To take the example from the post that started this > thread, the relationship between users and user profiles is "has-a", > not "is-a". So what would be the design benefit of applying > inheritance here in the first place?
I think whether it is a "has-a" or "is-a" relationship depends on the developer and the application. There's no reason for a developer not to extend User and reference their own User model instead of django's, if it makes more sense to them. Why make Profile models all over the place when you can just make User models and have all the syntactic sugar that comes with it, being able to treat it as a single entity? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
