Changes between Version 5 and Version 6 of Tutorial

Timestamp:

12/07/08 15:09:13 (5 years ago)

Author:

andrew

Comment:

--

Tutorial

@@ -131 +131 @@
 See how it's autodetected the model, and made the migration for us? Isn't that helpful?
 
+== Columns, Columns, Everywhere! ==
+
+Of course, most of your work won't be adding new tables, but rather new columns. As of version 0.4/revision [109], South has an `--add-field` option to `./manage.py startmigration`.
+
+Like the `--model` example above, you call startmigration with an app and migration name:
+
+{{{
+./manage.py startmigration app_name add_foo --add-field MyModel.foo
+}}}
+
+Note that you must provide the field name as `ModelName.field_name`, since South won't know what model you want otherwise! You should also have already written that column's definition in models.py.
+
+As with --model, you can use --add-field many times in a single call if you want to add a lot of columns:
+
+{{{
+./manage.py startmigration mitest some_cols --add-field user.age --add-field user.profile --add-field post.user
+}}}
+
+(also note here that you're free to write the model class names in lowercase; they're actually stored that way in Django)
+
 == All In One ==
 
@@ -161 +181 @@
 Some things you might want to try:
 
- * Writing a migration which adds a new column to a table (and removes it when rolled back). The [wiki:DatabaseAPI database api documentation] might help you here.
-
  * Adding a new migration with the wrong number - e.g. another 0002 migration when you already have a 0003 (just rename a 0004 if you use createmigration and it makes one). The resulting problem, and the resolutions, are discussed in [wiki:CommandReference#ConflictResolution the command reference].