@Javier,  not sure.. I've used user profiles on my past sites because that's
what I was told to do a while ago,   if inheritance works with
authentication and the admin,  I would definitely go that route.

Also, @Yanik,  I realized my UserProfile model example above was wrong,
the  user relation should be OneToOneField,   not ForeignKey.



On Thu, Sep 3, 2009 at 10:49 AM, Javier Guerra <jav...@guerrag.com> wrote:

>
> On Thu, Sep 3, 2009 at 10:41 AM, Ben Davis<bendavi...@gmail.com> wrote:
> > The django docs suggest using a UserProfile model when you need to add
> more
> > information about a user:
> >
> http://docs.djangoproject.com/en/dev/topics/auth/#storing-additional-information-about-users
>
> slightly OT: is there any advantage to use profiles instead of table
> inheritance?
>
> I know the userprofiles were the only choice before there was table
> inheritance; but is it still the best way?
>
> --
> Javier
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to