:mod:`migrate` - SQLAlchemy Migrate (schema change management)
.. module:: migrate
.. moduleauthor:: Evan Rosson
|Maintainer:||Domen Kožar <domenNO@SPAMdev.si>|
|Maintainer:||Jan Dittberner <jan.dittbernerNO@SPAMgooglemail.com>|
Inspired by Ruby on Rails' migrations, SQLAlchemy Migrate provides a way to deal with database schema changes in SQLAlchemy projects.
Migrate was started as part of Google's Summer of Code by Evan Rosson, mentored by Jonathan LaCour.
The project was taken over by a small group of volunteers when Evan had no free time for the project. It is now hosted as a Github project. During the hosting change the project was renamed to SQLAlchemy Migrate.
Currently, sqlalchemy-migrate supports Python versions from 2.6 to 2.7. SQLAlchemy Migrate 0.7.2 supports SQLAlchemy 0.6.x and 0.7.x branches.
Support for Python 2.4 and 2.5 as well as SQLAlchemy 0.5.x has been dropped after sqlalchemy-migrate 0.7.1.
Version 0.6 broke backward compatibility, please read :ref:`changelog <backwards-06>` for more info.
Download and Development
.. toctree:: download credits
|||(1, 2, 3, 4, 5) Table is renamed to temporary table, new table is created followed by INSERT statements.|
|||See http://www.sqlite.org/lang_altertable.html for more information. In cases not supported by sqlite, table is renamed to temporary table, new table is created followed by INSERT statements.|
|||You can not change datatype or rename column if table has NOT NULL data, see http://blogs.x2line.com/al/archive/2005/08/30/1231.aspx for more information.|
|||Changing nullable is not supported|
List of useful tutorials:
SQLAlchemy Migrate is split into two parts, database schema versioning (:mod:`migrate.versioning`) and database migration management (:mod:`migrate.changeset`). The versioning API is available as the :ref:`migrate <command-line-usage>` command.
.. toctree:: versioning changeset tools faq glossary
.. toctree:: api
.. toctree:: changelog