fe64667106
The "force" parameter in SQLAlchemy IdentifierPreparer.quote()
has been a no-op since 0.9 in
|
||
---|---|---|
doc/source | ||
migrate | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
COPYING | ||
doc-requirements.txt | ||
MANIFEST.in | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test_db_py3.cfg | ||
test_db.cfg | ||
test-requirements-py2.txt | ||
test-requirements-py3.txt | ||
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 readthedocs.org.
Users and developers can be found at #openstack-dev 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 openstack-dev 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:
- install tox:
pip install -U tox
- run tox:
tox
- to test only a specific Python version:
tox -e py27
(Python 2.7)
Please report any issues with sqlalchemy-migrate to the issue tracker at Launchpad issues