Hi, On Jul 31, 11:46 pm, Patrick Anderson <[EMAIL PROTECTED]> wrote: > I'd prefer not to hack the contrib.auth application and change User > model,
Adding just unique=true is not so hard and tracking with changes is easy :). You may have a look at the "Django tips: extending the User model" on The B List [1] > so perhaps that constraint should be included in my application > code, but I'm not sure what the best way to do it should be. I think that's a bit of too much overhead. I mean you already have a bunch of code that can handle this automaticaly. -- Amirouche --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
