#24429: Revise docs regarding non-int primary key on custom user models
-------------------------------+----------------------
Reporter: shadfc | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.8beta1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+----------------------
The docs
(https://docs.djangoproject.com/en/1.8/topics/auth/customizing/#specifying-a
-custom-user-model, point #1) say that a custom user model must have an
integer primary key but do not specify why.
https://code.djangoproject.com/ticket/24161 dealt with a session issue and
has been fixed.
I would like to be able to use a UUID as the pk for a custom user model
but this message makes me unsure if I should attempt that. Tim Graham
suggested opening a ticket to investigate this issue and either remove
that note from the docs or add a better explanation to it.
--
Ticket URL: <https://code.djangoproject.com/ticket/24429>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.f0621aa8cac502468cc2a277c193be36%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
