migrate --fake-initial fails to handle ManyToManyFields created by AddField

[tkhyn]

Hello,

I've run into an issue with Django 1.9's new migrate --run-syncdb command, which is supposed to replace syncdb. It does not seem to be related to #25884.

Basically, the workflow syncdb => makemigrations => migrate --fake-initial is broken when ManyToManyFields are used in models. Using any other field (even FKs) work fine.

I found out that when running migrate --fake-initial, MigrationExecutor.detect_soft_applied could not find a matching column for the M2M field in the existing table, and therefore considers that the initial migration has not been implicitly applied. My understanding is that migrate --run-syncdb failed to create that in the first place.

I have set up a minimal project to expose the issue:

• ​not working with Django 1.9
• ​working like a charm with Django 1.8

My use case ? ​django-gm2m's test suite needs to initialize individual apps one by one and sync the db before each TestCase (and then run migration tests from that state).

Thanks in advance for looking into this, and thanks already for all the work put in Django so far!

[Tim Graham]

​PR

[Tim Graham <timograham@…>]

In fa9ce4e9:

Fixed #25922 -- Fixed migrate --fake-initial detection of many-to-many tables.

[Tim Graham <timograham@…>]

In a80fb8a:

[1.9.x] Fixed #25922 -- Fixed migrate --fake-initial detection of many-to-many tables.

Backport of fa9ce4e9a691e4f8c8b093784bac752e488dc60b from master

[tkhyn]

Thanks a lot Tim, everything seems to work perfectly now.