On 10 November 2011 18:53, hcarvalhoalves <hcarvalhoal...@gmail.com> wrote: > I believe the solution is to actually figure a migration path to move > everything that is non-essential to outside the User model. To > identify a User, it should be enough to have username, password and > permissions, and have the rest of the fields live in a > django.contrib.auth.models.DefaultUserProfile.
Why do you want the password in the User-model? There are more ways of authenticating than user/password. There's openid, oauth, facebook, saml, cas, pam... One to one relationships *is* a well-known and respectable technique you know? I might have mentioned before that the only field that we can't do without in a User-model is the primary key. Everything else, even username, is up for grabs. HM -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
