#19354: Unable to set PK for custom user model
-------------------------------------+-------------------------------------
Reporter: markteisman@… | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version:
Severity: Normal | 1.5-alpha-1
Keywords: PK Primary Key | Resolution:
Custom User | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by claudep):
* easy: 0 => 1
* stage: Unreviewed => Accepted
Comment:
I think that in this case, replacing `id` by `pk` is trivial.
In the more general case, I'm not sure if we want to be completely id-
agnostic for the User model. There are places where it is currently
required to be an integer. It would also be useful to know why you
couldn't keep an autoincrement id, while keeping email unique.
--
Ticket URL: <https://code.djangoproject.com/ticket/19354#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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 https://groups.google.com/groups/opt_out.
