Hello community, here is the log from the commit of package python-alembic for openSUSE:Factory checked in at 2020-02-11 22:23:26 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-alembic (Old) and /work/SRC/openSUSE:Factory/.python-alembic.new.26092 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-alembic" Tue Feb 11 22:23:26 2020 rev:52 rq:772460 version:1.4.0 Changes: -------- --- /work/SRC/openSUSE:Factory/python-alembic/python-alembic.changes 2020-01-27 20:16:51.140501087 +0100 +++ /work/SRC/openSUSE:Factory/.python-alembic.new.26092/python-alembic.changes 2020-02-11 22:24:12.583528271 +0100 @@ -1,0 +2,47 @@ +Sat Feb 8 20:39:12 UTC 2020 - Arun Persaud <[email protected]> + +- update to version 1.4.0: + * feature + + Added new parameters BatchOperations.add_column.insert_before, + BatchOperations.add_column.insert_after which provide for + establishing the specific position in which a new column should + be placed. Also added + Operations.batch_alter_table.partial_reordering which allows the + complete set of columns to be reordered when the new table is + created. Both operations apply only to when batch mode is + recreating the whole table using recreate="always". Thanks to + Marcin Szymanski for assistance with the implementation. + References: #640 + * bug + + Adjusted the unique constraint comparison logic in a similar + manner as that of #421 did for indexes in order to take into + account SQLAlchemy’s own truncation of long constraint names + when a naming convention is in use. Without this step, a name + that is truncated by SQLAlchemy based on a unique constraint + naming convention or hardcoded name will not compare properly. + References: #647 + + A major rework of the “type comparison” logic is in place which + changes the entire approach by which column datatypes are + compared. Types are now compared based on the DDL string + generated by the metadata type vs. the datatype reflected from + the database. This means we compare types based on what would + actually render and additionally if elements of the types change + like string length, those changes are detected as well. False + positives like those generated between SQLAlchemy Boolean and + MySQL TINYINT should also be resolved. Thanks very much to Paul + Becotte for lots of hard work and patience on this one. See + also: What does Autogenerate Detect (and what does it not + detect?) - updated comments on type comparison References: #605 + * usecase + + Moved the use of the __file__ attribute at the base of the + Alembic package into the one place that it is specifically + needed, which is when the config attempts to locate the template + directory. This helps to allow Alembic to be fully importable in + environments that are using Python memory-only import + schemes. Pull request courtesy layday. References: #648 + * misc + + The internal inspection routines no longer use SQLAlchemy’s + Inspector.from_engine() method, which is expected to be + deprecated in 1.4. The inspect() function is now used. + +------------------------------------------------------------------- Old: ---- alembic-1.3.3.tar.gz New: ---- alembic-1.4.0.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-alembic.spec ++++++ --- /var/tmp/diff_new_pack.cXCmpH/_old 2020-02-11 22:24:13.091528549 +0100 +++ /var/tmp/diff_new_pack.cXCmpH/_new 2020-02-11 22:24:13.095528551 +0100 @@ -18,7 +18,7 @@ %{?!python_module:%define python_module() python-%{**} python3-%{**}} Name: python-alembic -Version: 1.3.3 +Version: 1.4.0 Release: 0 Summary: A database migration tool for SQLAlchemy License: MIT ++++++ alembic-1.3.3.tar.gz -> alembic-1.4.0.tar.gz ++++++ ++++ 3378 lines of diff (skipped)
