Yes, you should generate and apply migrations for the app that contains your custom user model. Since you skipped Django 1.7, you'll have to edit the automatically generated initial migration for that app and change EmailField max_length to 75 since that matches your schema. Then you can auto-generate a second migration to update the max_length to 254.
On Tuesday, April 21, 2015 at 11:42:45 AM UTC-4, Scott Hostovich wrote: > > I'm using a custom user model, so it seems that migration operations like > the following are ignored silently: > > migrations.AlterField( > model_name='user', > name='email', > field=models.EmailField(max_length=254, verbose_name='email address', > blank=True), > ), > > On Monday, April 20, 2015 at 4:19:56 PM UTC-4, Scott Hostovich wrote: >> >> I moving from Django 1.6 and south to Django 1.8. I followed the >> instructions at >> https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south >> >> and things seemed to work fine. Then I noticed that the auth migrations did >> not get applied to the database ( >> https://github.com/django/django/tree/1.8/django/contrib/auth/migrations >> ). >> >> Anyone else encounter this? >> > -- 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 http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/4ca1408a-f989-4032-b5b9-67244b6776d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
