On Tuesday, April 28, 2015 at 7:20:17 AM UTC+2, Mike Dewhirst wrote: > > Anyway, I suspect disabling migration - even if a > "master-switch" could be built - is undesirable if one is using any of > the django tables. > > > I'm not sure we're talking about the same.
Some of us don't need builtin migration system. It is badly designed, same as South was. I know that we can make simple migrations in seconds, but we're wasting hours elsewhere. Database migrations should be managed by database tool. "Model migrations" are fiction... this is a conceptual mistake. There are no models mapped to db tables - there are tables mapped to models. We're working with databases and their representations in application layer, and not vice versa. Thanks, Marcin -- 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+unsubscr...@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/de18bd57-ad18-4464-8783-009e26abced2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
