0👍
I believe this was because the migration scripts were getting called out of order, due to a problem I had setting them up. Everything is ok now.
0👍
Unless the new column has a default value defined, the insert statement will expect to add data to that column. Can you move the data load to be after the second migration. (I would have commented, but do not yet have sufficient reputation.)
- [Django]-How to customize [Authentication credentials were not provided] error message in Django rest framework
- [Django]-Implementing Name Synchronization and Money Transfers in Transactions Model with Account Number Input
- [Django]-How to combine select_related() and value()?
0👍
This happened to me because I faked one migration (m1), created another (m2), and then tried to migrate m2 before I had faked my initial migration (m1).
So in my case I had to migrate --fake <app name> m1 and then migrate <app name> m2.
0👍
I faced the same issue all what i do to get out this issue just drop all tables in my DB and then run:
python manage.py makemigrations
and :
python manage.py migrate