From e9f3306627c106d6b3848deceb00cc321465b627 Mon Sep 17 00:00:00 2001 From: Christopher Allan Webber Date: Fri, 28 Jun 2013 11:51:40 -0500 Subject: More clarifications on what ./bin/gmg dbupdate does on each run. This commit sponsored by Jessica Howard. Thanks, sistah! --- docs/source/devel/migrations.rst | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/source/devel/migrations.rst') 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 -- cgit v1.2.3