Yeah sure, i should have used "recommended" word instead of correct.
The difference between link i wrote and b-list is that the last one uses a foreign-key, while first uses one-to-one, and this is the way is recommended in doc, so... I think i will follow that post recommendations. Thanks again! p.d.: in this case, recommendation is not no use heritange, but, in cases where i want to extend ANOTHER app (3rd apps), how do you do it? using inheritange? On Mar 25, 9:30 pm, Mike Ramirez <gufym...@gmail.com> wrote: > On Friday, March 25, 2011 01:16:51 pm Nick Serra wrote:> Andre's solution is > out of date. Calvin is correct, use the user > > profile model that is built into django auth. OP, the link you found > > is correct. > > > >http://www.b-list.org/weblog/2006/jun/06/django-tips-extending-user-m... > > > > > > > here: > > > > > >http://docs.djangoproject.com/en/1.2//topics/auth/#storing- > > additional-information-about-users > > and: > > http://docs.djangoproject.com/en/1.3/topics/auth/#storing-additional- > information-about-users > > What's different about these pages, except that b-list goes into a bit more > detail? > > Hint: Nothing. > > But I don't think there is a "correct" way, just a recommended way. I use the > recommended way, but it's definately not the only way or 'better'. 'correct', > 'better' in this case are subjective to the needs of the dev and/or project. > > Mike. > > -- > Reality is just a convenient measure of complexity. > -- Alvy Ray Smith -- 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.
