x
/
sqlalchemy-migrate
Code Issues Proposed changes

fixed issue 129

This commit is contained in:
wyuenho@gmail.com 2011-10-02 20:13:10 +08:00
parent 4cb8fee5ff
commit 7ce76aaab6
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/versioning.rst
View File

@ -63,7 +63,7 @@ The database is specified as a `SQLAlchemy database url`_.
::
$ python my_repository/manage.py version_control sqlite:///project.db
$ python my_repository/manage.py version_control sqlite:///project.db my_repository
We can have any number of databases under this repository's version
control.
@ -72,7 +72,7 @@ Each schema has a version that SQLAlchemy Migrate manages. Each change
script applied to the database increments this version number. You can
see a database's current version::
$ python my_repository/manage.py db_version sqlite:///project.db
$ python my_repository/manage.py db_version sqlite:///project.db my_repository
0
A freshly versioned database begins at version 0 by default. This
@ -84,7 +84,7 @@ and applying change scripts changes the database's version number.
Similarly, we can also see the latest version available in a
repository with the command::
$ python my_repository/manage.py version
$ python my_repository/manage.py version my_repository
0
We've entered no changes so far, so our repository cannot upgrade a

2
migrate/versioning/api.py
View File

@ -119,7 +119,7 @@ def script_sql(database, description, repository, **opts):
For instance, manage.py script_sql postgresql description creates:
repository/versions/001_description_postgresql_upgrade.sql and
repository/versions/001_description_postgresql_postgres.sql
repository/versions/001_description_postgresql_downgrade.sql
"""
repo = Repository(repository)
repo.create_script_sql(database, description, **opts)