#24429: Revise docs regarding non-int primary key on custom user models
--------------------------------------+------------------------------------
Reporter: shadfc | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: 1.8beta1
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"993074d78d36875f984b5c2a53ef8a2547d392b5" 993074d]:
{{{
#!CommitTicketReference repository=""
revision="993074d78d36875f984b5c2a53ef8a2547d392b5"
[1.8.x] Fixed #24429 -- Doc'ed that Django 1.8 doesn't require an integer
PK for custom user models.
Backport of 981e3b9394022810bd536474344e2f91c190b858 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24429#comment:6>
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/064.a38e389efa4dd12b86aebb310c27b55e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
