summaryrefslogtreecommitdiff
path: root/README.rst
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2011-11-08 14:29:33 -0800
committerMike Bayer <mike_mp@zzzcomputing.com>2011-11-08 14:29:33 -0800
commit649b2629aef39707f3bcd3807b4574049226201d (patch)
tree9d0caa9b6b23b88600da01f6eb532cda6f3fdf27 /README.rst
parent08484e5dd5e117480766acf775a35ea59323c813 (diff)
downloadalembic-649b2629aef39707f3bcd3807b4574049226201d.tar.gz
blurb on auto gen
Diffstat (limited to 'README.rst')
-rw-r--r--README.rst10
1 files changed, 10 insertions, 0 deletions
diff --git a/README.rst b/README.rst
index 974846d..9b9dbc2 100644
--- a/README.rst
+++ b/README.rst
@@ -30,6 +30,16 @@ The goals of Alembic are:
structures for simple operations like these - the functions themselves
generate minimalist schema structures behind the scenes to achieve the given
DDL sequence.
+* "auto generation" of migrations, to the degree this is feasible. There
+ is a strong desire for migration tools that "figure out" what needs to
+ change automatically. While real world migrations are far more complex than
+ what can be automatically determined (thus contributing to the author's
+ skepticism of such tools), SQLAlchemy has mature and comprehensive schema
+ reflection capabilities, which should be used here. The tool will be
+ able to detect table adds/drops as well as column adds/drops/mutations,
+ and generate directives into new migration scripts automatically
+ for these operations. The migration script can then be edited as needed before
+ being run.
* Full support for migrations generated as SQL scripts. Those of us who
work in corporate environments know that direct access to DDL commands on a
production database is a rare privilege, and DBAs want textual SQL scripts.