#24679: Auth User last_login initialized as NULL from 1.8, old DB conflicts,
documentation update
-------------------------------+------------------------
Reporter: marktranchant | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Keywords: last_login
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+------------------------
In 1.8, there was a change to the User model where last_login is set to
{{{NULL}}} when a new user is created.
Databases created under older versions have a {{{NOT NULL}}} constraint on
the {{{last_login}}} column of {{{auth_user}}}. An app that tries to auto-
create a user non-interactively via {{{create_user()}}} will fail due to
the database conflict.
The 1.8 release notes do not refer (directly) to this change; the
Authentication documentation
[https://docs.djangoproject.com/en/1.8/ref/contrib/auth/#django.contrib.auth.models.User.last_login
mentions it in passing] but doesn't warn of the consequences.
This should be made clear in the release notes and in the Authentication
documentation. In my case, my test suite didn't pick it up because the
test database is created from scratch.
--
Ticket URL: <https://code.djangoproject.com/ticket/24679>
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/056.e5696b72d91a315e1ec292754b4964db%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
