diff options
| author | Christopher Allan Webber <cwebber@dustycloud.org> | 2013-06-28 11:51:40 -0500 |
|---|---|---|
| committer | Christopher Allan Webber <cwebber@dustycloud.org> | 2013-06-28 11:51:40 -0500 |
| commit | e9f3306627c106d6b3848deceb00cc321465b627 (patch) | |
| tree | d57294d56fa1583063f6363fcba5932918bfce87 | |
| parent | 4436fbcd01f4067dd335c0f2905f7fe841e3b301 (diff) | |
| download | mediagoblin-e9f3306627c106d6b3848deceb00cc321465b627.tar.lz mediagoblin-e9f3306627c106d6b3848deceb00cc321465b627.tar.xz mediagoblin-e9f3306627c106d6b3848deceb00cc321465b627.zip | |
More clarifications on what ./bin/gmg dbupdate does on each run.
This commit sponsored by Jessica Howard. Thanks, sistah!
| -rw-r--r-- | docs/source/devel/migrations.rst | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/source/devel/migrations.rst b/docs/source/devel/migrations.rst index bd9ac0da..16c02b04 100644 --- a/docs/source/devel/migrations.rst +++ b/docs/source/devel/migrations.rst @@ -20,6 +20,12 @@ structure works, we need to add a migration so that people running older codebases can have their databases updated to the new structure when they run `./bin/gmg dbupdate`. +The first time `./bin/gmg dbupdate` is run by a user, it creates the +tables at the current state that they're defined in models.py and sets +the migration number to the current migration... after all, migrations +only exist to get things to the current state of the db. After that, +every migration is run with dbupdate. + There's a few things you need to know: - We use `sqlalchemy-migrate |