Thomas Goirand f944414bd4 migrate needs subunit >= 0.0.18
The unit tests of subunit are failing with an older version of
subunit, so we need to fix the test-requirements.txt to reflect
the reality.

Change-Id: I786c70a02196b00fb0d96feb5fd1a0b5281f6672
2014-03-02 15:18:31 +08:00
2014-02-17 07:17:31 -08:00
2013-07-11 16:54:46 -04:00
2013-07-11 16:54:46 -04:00
2010-07-08 19:16:22 +02:00
2013-07-12 10:53:37 -04:00
2013-07-11 16:54:46 -04:00
2014-02-23 19:16:52 +00:00
2013-10-07 12:02:24 -04:00
2014-02-17 07:17:31 -08:00
2013-07-11 16:54:46 -04:00
2014-02-23 11:38:53 -05:00

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

Description
Database schema migration for SQLAlchemy
Readme 2.3 MiB
Languages
Python 99.3%
Shell 0.7%