4 ms·
I'd like to point out that this is just a first working version, and there's still some work left to do, but I'm very relieved this is finally merged!
by andrewgodwin 13y ago
I'd like to point out that this is just a first working version, and there's still some work left to do, but I'm very relieved this is finally merged!
- mattdeboard 13y agoIs this pluggable? Can users stick with South (or whatever migration backend) and still use the same API?
- andrewgodwin 13y agoNo, this is a complete rewrite and a different way of doing migrations than South currently does. There should also be a South 2 eventually that is mostly compatible with this new migration design, for those stuck on older Django.
- deleted 13y ago[deleted]
- famousactress 13y agoAndrew, is there info somewhere comparing the new stuff to current South in terms of what features differ etc? I'm particularly curious if there have been any changes to the way the orm freezing infra works.
- simonw 13y agoORM freezing is basically gone, in favour of a smarter approach where the previous state is derived from reading all of the previous migrations in to an in-memory data structure. Andrew's blog has some great write-ups of how the new system has evolved: http://www.aeracode.org/category/django-diaries/ http://www.aeracode.org/category/django-diaries/
- famousactress 13y agowow. I peeked, and that's gonna take me some time to wrap my head around. Really interesting approach. Does this mean though that if you ever fall out of favor w/ the db.migrations API and for instance make a manual change to a piece of schema, that the faked orm will be forever broken because it won't know about that change?
- metaphorm 13y agothank you kindly for this Andrew. South has been an indispensable tool for me and its wonderful to see it in django core.