A talk I gave at EuroDjangoCon 2009.
Migrations:whatwhyhowwho?http://www.flickr.com/photos/moonjazz/1216783552/
View Slide
I'm�Andrew.@andrewgodwinhttp://aeracode.org
mi·gra·tionwhatwhyhowwho?1.�nounA�way�to�keep�your�sanity�whenchanging�model�definitions.See�also:�Schema�Evolution
whatwhyhowwho?class Pony(models.Model ):name = models.CharField(max_length=100)height = models.IntegerField()class Pony(models.Model ):name = models.CharField(max_length=100)height = models.FloatField()born = models.DateField()
whatwhyhowwho?django.contrib.migrations
whatwhyhowwho?southmigratoryyadseldjango-evolutiondmigrationsdesebschema-evolution
whatwhyhowwho?django-evolution·�1½�years�old·�uses�syncdb�initially·�support�automatic�'hinting'
whatwhyhowwho?dmigrations·�8�months�old·�uses�migrations�from�start·�MySQL�only·�migrations�are�project-wide
whatwhyhowwho?south·�8�months�old·�uses�migrations�from�start·�supports�'autodetection'·�migrations�are�per-app·�mine
whatwhyhowwho?southdjango-evolutionvs
whatwhyhowwho?why?why?
whatwhyhowwho?south django-evolution1.�install3.�make�initial�����migration4.�migrate�to�initial2.�syncdb1.�install2.�syncdb
whatwhyhowwho?live�demoPonies!South!django-evolution!
whatwhyhowwho?thef�u�t�u�r�e
whatwhyhowwho?http://code.djangoproject.com/wiki/SchemaEvolutionhttp://south.aeracode.orghttp://code.google.com/p/django-evolution/
whatwhyhowwho?Thanks.Andrew�Godwinhttp://aeracode.org@andrewgodwin