Opened 17 years ago
Closed 17 years ago
#6466 closed (wontfix)
Using email as primary key for users
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Uncategorized | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Not being able to smoothly use email as primary key for users, instead of username, is the biggest (and single) showstopper to adopting Django I have. I am not sure what the solution would be, but I think you should be aware of the problem.
Thank you.
Change History (3)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
Also see a trivial workaround: http://www.djangosnippets.org/snippets/74/
comment:3 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
You're not required to use the supplied User
model, and there's no conceivable way that it could support every possible scheme of requirements someone could want. If you want to use Django's auth system with other requirements the preferred method is to write an auth backend as covered in the documentation.
See #3011