Thanks. Sorry. I have got to stop posting when I'm tired... For punishment, I read the Wikipedia article on the "@" character: http://en.wikipedia.org/wiki/@
No, I did not do a google search because I ass-umed the truly relevant info would be in this list. really. The first Google hit is a Django snippet, and while the solution might not be global like I want it does point out a potential problem. In that there already is an e-mail field and having duplicate data in the two fields could break some applications. Which makes me wonder if the "right" way is to use a custom user validation system, likely with the e-mail field dropped, or maybe just aliased to the username so things that expect e-mail address find one. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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=.
