"OperationalError: (1054, "Unknown column ...)" error when running migrations on an empty MySQL database.

[coolnodje]

I keep hitting this problem while trying to replay an entire database migrations on a new fresh DB (from MySQL to PostgreSQL to be precise).

MySQL complains of a non existing column that was removed in a later stage of migrations.
This column doesn't exist in MySQL anymore as it is up to date with the newest migration. So it's only natural that the column cannot be found.

The question is: why is migrate looking for this column at this stage? It can only be found in the target new DB.

I'm not including any code at this stage but I guess I can probably find a way to share the whole migrations if this doesn't sound like an already addressed problem.

[Mariusz Felisiak]

Thanks for this report, however we will not be able to reproduce this issue (or check if it is a duplicate of an existing one) without a small sample project or more detailed report.