Migration generation order is wrong when using existing fields

Hi @ldc,

I believe this is the same issue (or perhaps an expanded explanation?) as the other post, right? Bug: Autogenerating and running migrations tries to generate schema_migration model twice - #7 by roger

We noticed the same thing as you there, and have filed a bug report about it. It is currently awaiting developer investigation, and I’ll let you know once we have any new findings.

If these are indeed the same issue, is it OK with you if I merge the two threads? Or if I misunderstood and this is a different scenario, please let me know.

Thank you again for your report and patience with this! Sorry for the inconvenience.