#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
-------------------------------+--------------------------------------
Comment (by marktranchant):
Thanks. Looks like a prior migration failed in my case due to a manually-
caused discrepancy between dev and prod DBs, so I hadn't noticed this
hadn't run.
However, I still think there's a communication issue. I've been using
Django for six years, and hit this problem despite that experience. The
release notes reference AbstractUser, which I didn't recognize as
something I'm using (base class for User).
--
Ticket URL: <https://code.djangoproject.com/ticket/24679#comment:2>
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.2eb789047ee22e45766e9d0571754285%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
