On Monday 27 April 2009 20:12:13 karl wrote: > > Apologies in advance, I'm sure this query pops up regularly. > > > > I'd like to replace the default User class which comes with Django's > > authentication system (for my application, users login via > > email/password, not login/password, so it's not only a matter of adding > > fields). > > > > Is there an easy way to do it? Or should I just roll my own and give on > > the default authentication system and (sniff) admin site? > > This blog article explains it simply and has ready-to-use code: > > http://www.davidcramer.net/code/224/logging-in-with-email-addresses-in- djan >go.html
Very nice and useful. However, it suffers from a simple flaw: the default Django user model does not guarantee the uniqueness of email addresses, which is a problem when you need it as primary key. Sorry for not having made this point more clearly, but this is why I was talking about replacing Django's default model. Do you know if there is a way around this? Cheers, Emm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
