Re:Schema migrations merged into Django master
by j4mie on Friday August 23, 2013 @08:23AM
(#6263005)
And here are the docs: https://docs.djangoproject.com/en/dev/topics/migrations/
[ Parent
| on HN ]
Re:Schema migrations merged into Django master
by japhyr on Friday August 23, 2013 @09:15AM
(#6263275)
Migrations are per-app, but the command is shown as
python manage.py makemigrations
Using South, it was python manage.py schemamigration app_name
How does django know which app to build migrations for?
Re:Schema migrations merged into Django master
by andrewgodwin on Friday August 23, 2013 @09:20AM
(#6263314)
It does them all at once. The new system knows about interdependencies, so if you have ForeignKeys between apps it'll make all of them in the right order.
Re:Schema migrations merged into Django master
by antihero on Saturday August 24, 2013 @03:26AM
(#6268007)
Has it solved that issue where say I have a TinyMCE field, then I ditch TinyMCE and use CKEditor, that I'd still need TinyMCE installed in order to do the old migration, despite it just being a TextField database-wise?
Re:Schema migrations merged into Django master
by arocks on Friday August 23, 2013 @09:37AM
(#6263465)
So if I understand correctly, "makemigrations" will convert all apps to use migrations except apps which were created using previous versions of Django?
Re:Schema migrations merged into Django master
by andrewgodwin on Friday August 23, 2013 @09:41AM
(#6263499)
It will prompt you if an app doesn't yet have migrations and ask if you want it to. That prompt is currently a bit aggressive - asking you every time - but that will be fixed soon.