Code

Opened 6 years ago

Closed 6 years ago

#6466 closed (wontfix)

Using email as primary key for users

Reported by: pupeno@… Owned by: nobody
Component: Uncategorized Version: master
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

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.

Attachments (0)

Change History (3)

comment:1 Changed 6 years ago by ramiro

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

See #3011

comment:2 Changed 6 years ago by mattmcc

Also see a trivial workaround: http://www.djangosnippets.org/snippets/74/

comment:3 Changed 6 years ago by ubernostrum

  • Resolution set to wontfix
  • Status changed from new to 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.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.