| 159 | | This tutorial needs more work, but it's lunchtime and I'm hungry. In the meantime, I suggest creating more migrations to do things like rename columns (but never forget to change your models to match), and try renaming new migrations so they haven't been applied but should have, and see how South asks you to resolve this (don't worry, the error messages are very helpful!) |
| | 159 | This tutorial needs more work; if you feel like adding something, please do! |
| | 160 | |
| | 161 | Some things you might want to try: |
| | 162 | |
| | 163 | * 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. |
| | 164 | |
| | 165 | * 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]. |