Accepting request 835581 from home:apersaud:branches:devel:languages:python

update to latest version

OBS-URL: https://build.opensuse.org/request/show/835581
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-alembic?expand=0&rev=113

python-alembic.changes

@@ -1,3 +1,41 @@
+-------------------------------------------------------------------
+Sat Sep 19 15:30:06 UTC 2020 - Arun Persaud <arun@gmx.de>
+
+- 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
+
 -------------------------------------------------------------------
 Sat Mar 28 16:27:08 UTC 2020 - Arun Persaud <arun@gmx.de>