summaryrefslogtreecommitdiffstats
path: root/meta-python/recipes-devtools/python/python3-alembic_1.5.2.bb
Commit message (Collapse)AuthorAgeFilesLines
* python3-alembic: Upgrade 1.5.2 -> 1.5.3Leon Anavi2021-02-021-16/+0
| | | | | | | | | | | | | | | | | | | | | 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>
* python3-alembic: Upgrade 1.5.1 -> 1.5.2Leon Anavi2021-01-251-0/+16
Upgrade to release 1.5.2: - Fixed regression where new "loop detection" feature produced false positives for revision names that have overlapping substrings between revision number and down revision and/or dependency, if the downrev/dependency were not in sequence form. - Fixed regression where Alembic would fail to create a transaction properly if the sqlalchemy.engine.Connection were a so-called "branched" connection, that is, one where the .connect() method had been called to create a "sub" connection. 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>