Sorry for the belated reply, Andrew and Curtis.
You're both right that the "bug" was just a case of makemigrations
resolving dependency issues and my misunderstanding of that fact.
To test whether this was a bug or just makemigrations splitting up the
migration, I had created a separate app wit
Indeed, Django can make many migrations for an initial set if it needs them
to de-circularise dependencies (e.g. two models with foreign keys pointing
at each other - it splits one of their FKs into a second migration).
Andrew
On Sun, Feb 8, 2015 at 11:17 PM, Curtis Maloney
wrote:
> Could you p
Could you provide details about what sort of field you added, please?
I have seen cases where migrations will create two separate migrations for
an initial.
--
Curtis
On 9 February 2015 at 10:11, Yo-Yo Ma wrote:
> Using Python 3.4.2 and Django @stable/1.8.x (installed just moments before
> thi
Using Python 3.4.2 and Django @stable/1.8.x (installed just moments before
this writing), I created a model with a "name" field, then created a
migration for it. Moments after, I added an "age" field to the model,
deleted the 0001_initial.py migration, deleted __pycache__ directories in
my enti
