| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Upgrade to release 1.5.4:
- Fixed bug in versioning model where a downgrade across a
revision with a dependency on another branch, yet an ancestor
is also dependent on that branch, would produce an erroneous
state in the alembic_version table, making upgrades impossible
without manually repairing the table.
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Acked-by: Trevor Gamblin <trevor.gamblin@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
Upgrade to release 1.5.3:
- Changed the default ordering of “CREATE” and “DROP” statements
indexes and unique constraints within the autogenerate process,
so that for example in an upgrade() operation, a particular
index or constraint that is to be replaced such as for a casing
convention change will not produce any naming conflicts. For
foreign key constraint objects, this is already how constraints
are ordered, and for table objects, users would normally want to
use Operations.rename_table() in any case.
- Fixed assorted autogenerate issues with SQL Server.
- Fixed issue where autogenerate rendering of op.alter_column()
would fail to include MySQL existing_nullable=False if the column
were part of a primary key constraint within the table metadata.
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Acked-by: Trevor Gamblin <trevor.gamblin@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
