#24679: Auth User last_login initialized as NULL from 1.8, old DB conflicts,
documentation update
-------------------------------+--------------------------------------
Reporter: marktranchant | Owner: nobody
Type: Bug | Status: closed
Component: Documentation | Version: 1.8
Severity: Normal | Resolution: invalid
Keywords: last_login | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by bmispelon):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
Hi,
A migration was shipped alongside this change and you should make sure
it's run, as documented in the release notes:
https://docs.djangoproject.com/en/1.8/releases/1.8/#abstractuser-last-
login-allows-null-values.
This should fix the database conflicts that you mention.
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/24679#comment:1>
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/071.199e2660cd7a9a0195678584dbc422a5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
