938757e7aa
Now that we don't run SQL script with a single .execute() call, transaction management statements (BEGIN, COMMIT, END) fail with operational error. Ignore them if occurred in a script. All in all, transactions are managed by SQLAlchemy-migrate itself, so there is no reason for the calling code to pass those statements in a SQL script. Warn user about the statements that are ignored. The ideal response to such a warning from library users is removing those redundant transaction management statements from their scripts. Note: ROLLBACK is not ignored even though it's one of transaction management statements because its usage in migration scripts is insane anyway, and we're better fail on it and not (almost) silently ignore it. Change-Id: Ie4179c0e9341d42656d66821aaac23f8dcd33927 Closes-bug: 1368391
sqlalchemy-migrate
Fork from http://code.google.com/p/sqlalchemy-migrate/ to get it working with SQLAlchemy 0.8.
Inspired by Ruby on Rails' migrations, Migrate provides a way to deal with database schema changes in SQLAlchemy projects.
Migrate extends SQLAlchemy to have database changeset handling. It provides a database change repository mechanism which can be used from the command line as well as from inside python code.
Help
Sphinx documentation is available at the project page packages.python.org.
Users and developers can be found at #sqlalchemy-migrate on Freenode IRC network and at the public users mailing list migrate-users.
New releases and major changes are announced at the public announce mailing list migrate-announce and at the Python package index sqlalchemy-migrate.
Homepage is located at stackforge
You can also clone a current development version
Tests and Bugs
To run automated tests:
- Copy test_db.cfg.tmpl to test_db.cfg
- Edit test_db.cfg with database connection strings suitable for running tests. (Use empty databases.)
- $ pip install -r requirements.txt -r test-requirements.txt
- $ python setup.py develop
- $ testr run --parallel
Please report any issues with sqlalchemy-migrate to the issue tracker at code.google.com issues