Re: Different auth user models withoout doing multi-table inheritance

Hi James, thanks for the elaborate answer. Not that explicit OneToOne relationships are bad but I was just trying to avoid the overhead due to the JOINs that comes with it.

Understood. Unless you specifically request the data either by accessing the .merchant_data FK attribute or use select_related(), you shouldn't see a JOIN. I stumbled across this video yesterday where Russell talks about the user model and having only minimal authentication data in the primary model vs. profile data in ancillary models, along with a bunch of other fun topics like tracking names and genders within the user models.

http://www.rightrelevance.com/search/articles/hero?article=20db948267aa29156a7ca20a83b66d54a2953f19&query=django&taccount=django_rr

-James

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2Be%2BciVZvsaccR3G6b%3DrJi8WApHE-bXNzthxHtJcCavB66VRUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.