Hi everyone,

we are trying in our application to support multiple Django versions, 
specifically 1.7 to 1.9. But we encountered a problem with 
`User.last_login` field. We use custom User model based on 
`AbstractBaseUser` as specified by the documentation. Everything was fine 
in Django 1.7, but we got stuck when we wanted to add support for Django 
1.8, where the `last_login` was modified to allow NULL values. As 
recommended by 
we have migrations generated in Django 1.7 (lowest supported version) an 
thus `last_login` is NOT NULL, but that causes tests to fail when run in 
Django 1.8/1.9, since code allows `last_login` to be NULL.

We can't even redefine the field in our model, which would be the most 
straight forward solution, but that's not allowed by Django either.

What's the correct solution for this problem? It looks to us like there are 
some unresolved issues regarding the model and migrations design.

Thanks for any suggestions

You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to