The auth app includes support to use a profile model, configured with AUTH_PROFILE_MODULE in settings, which the docs show you how to use. Yes you can use inheritance, but you might assume it is a good idea to use what the auth app promotes.
On Fri, Mar 25, 2011 at 9:04 AM, Antonio Sánchez <adonis28...@gmail.com> wrote: > > hi! i have a question, which is the best option about extending user model?? > here: > http://docs.djangoproject.com/en/1.2//topics/auth/#storing-additional-information-about-users > they say to create a manual OneToOneField between models and some more stuff, > but here: > http://docs.djangoproject.com/en/1.2//topics/db/models/#multi-table-inheritance > it says that with inheritance this 1:1 relationship is created automatically, > both are in django docs > > appart from this, i have read a lot ways, some people inherit, other use > foreign key, ones redefines django's authentication backend other rewrites > pre-save/save methods... :S ... so, which way do you think is better (some > tutorial/blog post/something)?? thanks! > > djjango’s authentication backend. > > -- > 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. -- Read my blog! I depend on your acceptance of my opinion! I am interesting! http://techblog.ironfroggy.com/ Follow me if you're into that sort of thing: http://www.twitter.com/ironfroggy -- 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.
