More clarifications on what ./bin/gmg dbupdate does on each run.

This commit sponsored by Jessica Howard.  Thanks, sistah!

diff --git a/docs/source/devel/migrations.rst b/docs/source/devel/migrations.rst
index bd9ac0daa3c8cb97a32923d540be09c2384751a0..16c02b04846bb39288fac308a2028d3174ba5eca 100644 (file)
--- 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