Hello community, here is the log from the commit of package python-alembic for openSUSE:Factory checked in at 2020-09-21 17:42:51 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-alembic (Old) and /work/SRC/openSUSE:Factory/.python-alembic.new.4249 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-alembic" Mon Sep 21 17:42:51 2020 rev:55 rq:835584 version:1.4.3 Changes: -------- --- /work/SRC/openSUSE:Factory/python-alembic/python-alembic.changes 2020-03-29 14:27:44.750160409 +0200 +++ /work/SRC/openSUSE:Factory/.python-alembic.new.4249/python-alembic.changes 2020-09-21 17:45:03.593005563 +0200 @@ -1,0 +2,38 @@ +Sat Sep 19 15:30:06 UTC 2020 - Arun Persaud <[email protected]> + +- update to version 1.4.3: + * bug + + Added support to drop named CHECK constraints that are specified + as part of a column, rather than table wide. Previously, only + constraints associated with the table were considered. + References: #711 + + Fixed issue where the MySQL dialect would not correctly render + the server default of a column in an alter operation, if the + operation were programmatically generated from an autogenerate + pass as it would not accommodate for the full structure of the + DefaultClause construct. References: #736 + + Fixed issue where the CAST applied to a JSON column when copying + a SQLite table during batch mode would cause the data to be + lost, as SQLite’s CAST with JSON appears to convert the data to + the value “0”. The CAST is now skipped in a dialect-specific + manner, including for JSON columns on SQLite. Pull request + courtesy Sebastián Ramírez. References: #697 + + The alembic current command no longer creates an alembic_version + table in the database if one does not exist already, returning + no version as the current version. This allows checking for + migrations in parallel without introducing race conditions. Pull + request courtesy Nikolay Edigaryev. References: #694 + + Fixed issue where columns in a foreign-key referenced table + would be replaced with null-type columns during a batch + operation; while this did not generally have any side effects, + it could theoretically impact a batch operation that also + targets that table directly and also would interfere with future + changes to the .append_column() method to disallow implicit + replacement of columns. + + Fixed issue where the mssql_drop_foreign_key=True flag on + op.drop_column would lead to incorrect syntax error due to a + typo in the SQL emitted, same typo was present in the test as + well so it was not detected. Pull request courtesy Oleg + Shigorin. References: #716 + +------------------------------------------------------------------- Old: ---- alembic-1.4.2.tar.gz New: ---- alembic-1.4.3.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-alembic.spec ++++++ --- /var/tmp/diff_new_pack.zwDULG/_old 2020-09-21 17:45:05.829007670 +0200 +++ /var/tmp/diff_new_pack.zwDULG/_new 2020-09-21 17:45:05.829007670 +0200 @@ -18,7 +18,7 @@ %{?!python_module:%define python_module() python-%{**} python3-%{**}} Name: python-alembic -Version: 1.4.2 +Version: 1.4.3 Release: 0 Summary: A database migration tool for SQLAlchemy License: MIT ++++++ alembic-1.4.2.tar.gz -> alembic-1.4.3.tar.gz ++++++ ++++ 28233 lines of diff (skipped)
