On Tue, Mar 25, 2014 at 4:02 PM, Florian Apolloner <[email protected]>wrote:
> On Tuesday, March 25, 2014 9:12:42 PM UTC+1, Andrew Godwin wrote: >> >> So, the functionality whereby you can have apps which do not use >> migrations (i.e. that use the old creation backends) is meant to go away in >> 1.9. >> > > Uhm, strong -1 here unless you have really convincing arguments, I really > wouldn't like to require migrations for all the models we have in our own > testsuite. Especially since they are somewhat transient and don't have to > care about migrations. > > We can possibly work around it for the test suite, but the intention was that all apps people build on Django would require migrations by that point, as then we can get rid of a whole load of legacy code. There's nothing to stop us just making something that just migrates models for tests without files on disk, but it'd still have to be making Migration objects in memory behind the scenes due to any potential dependency/foreignkey issues (the syncdb code only gets around this by doing everything in one huge transaction, which isn't the model that SchemaEditor supports). Separate from all that, though, we can't promote adding random strings to MIGRATION_MODULES as the suggested way to "get around" migrations for tests. In my opinion, the whole point of migrations is that you know you have the same schema everywhere, and it's especially important you use them during tests. Andrew -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFwN1uqOy46SRBg0BM2XgwhWTFrWu5my49ScsrwD4eCKcWOqsA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
