When the library now has table, a field of migration problems, you can use python manager makemigrations --fake to create a new django at initialization file, and then add fields to delete the file, and then execute python manager makemigrations xxx (app name )
Python Manager the migrate xxx (App name)
August 14, 2019 22:53:54
Back when the accident change project code, the first step makemigrations account on some machines prompt settings tables are missing from other machines on the settings table dump down and then the first step makemigrations account, then migrate account. If you then migrate to other app directly makemigrations table, it will complain, settings table already exists, somehow. Although the migration script successfully, but migrate when the error.
Solution: In the first step before execution, source table into the settings migration In the third step before the other app, delete the settings table. Successful migration,
due to join the license verification code, so when in use will judge broke the poc. Poc need to comment out this logic. To start project