Indeed this was the problem.
Thanks for your answer and I got it through IRC too.
Have a good day
On 04/21/2015 07:13 PM, Tim Graham wrote:
This seems to be a common point of confusion. I'll add a sentence to
release notes under the "``AbstractUser.last_login`` allows null
values" section --
This seems to be a common point of confusion. I'll add a sentence to
release notes under the "``AbstractUser.last_login`` allows null values"
section -- if this makes sense:
If you are using a custom user model, you'll need to run
:djadmin:`makemigrations` and generate a migration for your app.
Hello,
I'm upgrading my systems to Django 1.8 and I'm facing this error:
(1048, "Column 'last_login' cannot be null")
so I describe my table in DB:
+-+--+--+-+-++
| Field | Type | Null | Key | Default |
3 matches
Mail list logo