fe148d87b4
migrate can't just take a global requirements sync because it needs to be tested against multiple versions of SQLA to assure compatibility. A recent change had the effect of only testing migrate against SQLA 0.7, which is definitely *not* what we want to be doing. this reverts that change, and leaves very specific comments to hopefully prevent this from happening in the future. Change-Id: Icb4e136f0de6caa224019bb955341c4b67c5e1a1 |
||
|---|---|---|
| doc/source | ||
| migrate | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| COPYING | ||
| doc-requirements.txt | ||
| MANIFEST.in | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test_db.cfg | ||
| test-requirements.txt | ||
| TODO | ||
| tox.ini | ||
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