#14881: [nonrel] Do not assume ``User.id`` to be an integer in
django.contrib.auth's pasword reset feature
------------------------------+-----------------------------------------
Reporter: jonash | Owner: nobody
Type: New feature | Status: new
Component: contrib.auth | Version: SVN
Severity: Normal | Resolution:
Keywords: nonrel | Triage Stage: Someday/Maybe
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
------------------------------+-----------------------------------------
Comment (by anonymous):
Replying to [comment:6 jezdez]:
> I don't see a reason to support non-integer IDs in 1.3 since none of the
core ORM backends support that kind of thing.
People want to use Django with non-rel backends not in core today. That's
what this patch allows.
The patch seems straightforward, the only big issue I can see is that it
breaks already generated password resets. Is that an OK backwards
incompatibility tradeoff to get the possibility to do auth with non-rel
backends?
--
Ticket URL: <https://code.djangoproject.com/ticket/14881#comment:12>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
