suggestion:
Add in the following after the cell:
$ python manage.py convert_to_south blog
Display what it should show in output:
"$ python manage.py convert_to_south blog
Creating migrations directory at ...
Creating init.py in ...
Added model blog.Entry
Added model blog.Comment
Created 0001_initial.py. You can now apply this migration with: ./manage.py migrate blog
Soft matched migration 0001 to 0001_initial.
Running migrations for blog:
Migrating forwards to 0001_initial.
blog:0001_initial
(faked)
App 'blog' converted. Note that South assumed the application's models matched the database
(i.e. you haven't changed it since last syncdb); if you have, you should delete the blog/migrations
directory, revert models.py so it matches the database, and try again."
Also, note that it prompted me to "You can now apply this migration..." Shouldn't we include explanation about this statement, just in case if someone is wondering?
When I applied migration, it gave me the following:
"$ python manage.py migrate blog
Running migrations for blog:
Nothing to migrate.
Loading initial data for blog.
Installed 0 object(s) from 0 fixture(s)"
suggestion: Add in the following after the cell: $ python manage.py convert_to_south blog
Display what it should show in output: "$ python manage.py convert_to_south blog Creating migrations directory at ... Creating init.py in ...
App 'blog' converted. Note that South assumed the application's models matched the database (i.e. you haven't changed it since last syncdb); if you have, you should delete the blog/migrations directory, revert models.py so it matches the database, and try again."
Also, note that it prompted me to "You can now apply this migration..." Shouldn't we include explanation about this statement, just in case if someone is wondering?
When I applied migration, it gave me the following: "$ python manage.py migrate blog Running migrations for blog: