On Tue, Jan 13, 2009 at 9:14 PM, ldm999 <malcolm.le...@gmail.com> wrote:
> > I need some extra fields on User and my first assumption was I could > subclass user (yes, I am a newbie). Then I read the docs and they talk > about using UserProfile. This article (http://scottbarnham.com/blog/ > 2008/08/21/extending-the-django-user-model-with-inheritance/ > #comment-621<http://scottbarnham.com/blog/2008/08/21/extending-the-django-user-model-with-inheritance/#comment-621>) > seems to say that following some recent improvements in > inheritance support, inheritance is now the better way to go. It > certainly sounds attractive to me. Eg I only need one form to edit > profiles instead of two. > > My immediate requirements are: > > 1) Extend the User model and provide custom forms to add/edit my > custom users > 2) Use groups to create user groups > > So, here's my question: What are the specific reasons, if any, why I > should NOT use model inheritance to extend my User model? > Malcolm's recent reply on a different thread seems relevant to what you are asking: http://groups.google.com/group/django-users/msg/baa3afd55b14ad68 Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
