I have read a lot of other posts here on stackoverflow and google but I could not find a solution.
It all started when I changed the model from a CharField to a For
I solved it by just adding null = True
to both the (automatically generated) migration file that was causing the issue and in the Model. Then migrate
again and your failed migration will now succeed. As you changed it also in your model, makemigration
will detect no changes after that.
I solved it by below:
venue_city = models.CharField(blank=True, null=True)
makemigrations
and migrate
commandHad a similar problem i resolved it by removing the previous migration files.No technical explanation
Looks like you added null=True
after created migration file. Because venue_city
is not a nullable field in your migration file
Follow these steps.
1) Drop venue_city & venue_country from your local table
3) Delete all the migration files you created for these `CharField to a ForeignKey` change
4) execute `python manage.py makemigrations`
5) execute 'python manage.py migrate'
It should work
follow the below steps:-
no need to drop table or remove migrations from migration tables