[Answered ]-Django – Migrate command says that table exists after second makemigrations was executed

This will never happen unless django detects (thinks) that the database has not been setup, and tries to initialise the tables with a schema.

Looks like your tables are already setup, but this is not known to django. That is why it tries to start applying the first migration – the table creation and schema is included in that.

You can use the --fake and --fake-initial options as per your specific problem, which tell django that the tables are already setup and ready, and to fake the migrations.

Useful links for more info:

django migrations – django documentation

django migrations, a primer – realpython

how to redo a migration after fake – stackoverflow