Block alembic 1.6.3
As described in [1], since #844 was introduced, when a table is created, all columns "index" and "unique" flags are unset. In 1.6.4 [2], "CreateTableOp" sets the flag "_constraints_included" to False by default. That will honor the "index" and "unique" flags set in each column definition. Related-Bug: #1929518 [1]https://github.com/sqlalchemy/alembic/issues/848 [2]https://gerrit.sqlalchemy.org/c/sqlalchemy/alembic/+/2839 Change-Id: I90380b027cade633088099ae766ff5c116014cea
This commit is contained in:
parent
bc4ca285cb
commit
7577743d00
@ -1,5 +1,5 @@
|
||||
abclient # Apache-2.0
|
||||
alembic!=1.2.0 # MIT
|
||||
alembic!=1.2.0,!=1.6.3 # MIT
|
||||
amqp!=2.1.4,!=5.0.4 # BSD
|
||||
ansible-runner!=1.3.5 # Apache 2.0
|
||||
anyjson # BSD
|
||||
|
@ -534,7 +534,7 @@ futurist===2.3.0
|
||||
jsonschema===3.2.0
|
||||
sphinxcontrib-devhelp===1.0.2
|
||||
python-blazarclient===3.2.0
|
||||
alembic===1.6.3
|
||||
alembic===1.6.2
|
||||
execnet===1.8.0
|
||||
glance-store===2.5.0
|
||||
sphinxcontrib-programoutput===0.17
|
||||
|
Loading…
Reference in New Issue
Block a user