Should squashmigrations produce a migration that could be improved by editing?

Hi Folks,

I recently squashed 93 migrations down to 1 in order to improve the speed at which tests ran. (5 tests took about 70 seconds to run before. Now they take 13.) I noticed that the resulting migration had a large list of small operations, mostly migration.AddField. What I have two questions:

1) Is it likely worth the effort to decrease the time it takes for the test runner to spin up the test database by pushing these operations into just a few and are there any tripwires I should be aware of in doing so? 

2) I did need to re-order two CreateModel operations in order to get this migration to run because a model was created before one on which it had a ForeignKey relation. I suspect this of being a bug someone would have run into already but a couple searches show one hasn't been filed don't turn up anything. Does this sound familiar to anyone or should I file a new ticket?

This project is currently running

python=2.7.9
django==1.7.7

cheers,

Andrew

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2By5TLbtiPwoA3kdmx6HknP2F%3DvztAGf8Ebtp%3D2oNEvS1WT6iQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.