Re: why django 1.9 migrations are essential?

use "manage.py test --keepdb" (available since 1.8)

Re: why django 1.9 migrations are essential?

Yes, as Tim says, 1.9 actually introduces the ability to mark apps as not having migrations; we specifically chose to keep supporting the migration-less creation format, just as an explicit setting. Note that you can't give an app migrations normally but run the tests without them; for correctness

Re: why django 1.9 migrations are essential?

Hi, have you read the 1.9 release notes? Specifically, "When supplying None as a value in MIGRATION_MODULES , Django will consider the app an app without migrations." If so, maybe we need a better description of

Re: why django 1.9 migrations are essential?

On Wed, Nov 11, 2015, at 16:47, skyjur wrote: > Back before django got migrations with south it was possible to do: > > syncdb --all (create all tables old way)   migrate --fake (mark all > migrations done) Keep in mind that these are not equivalent to running `migrate`. Data migrations would nev

why django 1.9 migrations are essential?

Back before django got migrations with south it was possible to do: syncdb --all (create all tables old way) migrate --fake (mark all migrations done) This flow was very useful in tests as well as when setting up new projects. I'm a bit confused to as to why django took this route and in 1