py-alembic: updated to 1.4.2

1.4.2:
bug

[bug] [tests]

Fixed an issue that prevented the test suite from running with the recently released py.test 5.4.0.

[bug] [autogenerate] [mysql]

Fixed more false-positive failures produced by the new “compare type” logic first added in 605, particularly impacting MySQL string types regarding flags such as “charset” and “collation”.

[bug] [op directives] [oracle]

Fixed issue in Oracle backend where a table RENAME with a schema-qualified name would include the schema in the “to” portion, which is rejected by Oracle.

usecase

[usecase] [autogenerate]

Adjusted autogen comparison to accommodate for backends that support computed column reflection, dependent on SQLAlchemy version 1.3.16 or higher. This emits a warning if the SQL expression inside of a Computed value changes between the metadata and the database, as these expressions can’t be changed without dropping and recreating the column.


1.4.1
bug

[bug] [autogenerate]

Fixed regression caused by the new “type comparison” logic introduced in 1.4 as part of 605 where comparisons of MySQL “unsigned integer” datatypes would produce false positives, as the regular expression logic was not correctly parsing the “unsigned” token when MySQL’s default display width would be returned by the database. Pull request courtesy Paul Becotte.

[bug] [environment]

Error message for “path doesn’t exist” when loading up script environment now displays the absolute path. Pull request courtesy Rowan Hart.

[bug] [autogenerate]

Fixed regression in 1.4.0 due to 647 where unique constraint comparison with mixed case constraint names while not using a naming convention would produce false positives during autogenerate.

[bug] [environment]

The check for matched rowcount when the alembic_version table is updated or deleted from is now conditional based on whether or not the dialect supports the concept of “rowcount” for UPDATE or DELETE rows matched. Some third party dialects do not support this concept. Pull request courtesy Ke Zhu.

[bug] [operations]

Fixed long-standing bug where an inline column CHECK constraint would not be rendered within an “ADD COLUMN” operation. The DDL compiler is now consulted for inline constraints within the Operations.add_column() method as is done for regular CREATE TABLE operations.

2 files changed, 7 insertions, 7 deletions

diff --git a/databases/py-alembic/Makefile b/databases/py-alembic/Makefile
index 63ff9502bdc..5bc78b4a4d7 100644
--- a/databases/py-alembic/Makefile
+++ b/databases/py-alembic/Makefile
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.21 2020/02/16 21:11:41 adam Exp $
+# $NetBSD: Makefile,v 1.22 2020/04/10 08:02:04 adam Exp $
 
-DISTNAME=	alembic-1.4.0
+DISTNAME=	alembic-1.4.2
 PKGNAME=	${PYPKGPREFIX}-${DISTNAME}
 CATEGORIES=	databases python
 MASTER_SITES=	${MASTER_SITE_PYPI:=a/alembic/}
diff --git a/databases/py-alembic/distinfo b/databases/py-alembic/distinfo
index b99ea812d71..d632725d31d 100644
--- a/databases/py-alembic/distinfo
+++ b/databases/py-alembic/distinfo
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.20 2020/02/16 21:11:41 adam Exp $
+$NetBSD: distinfo,v 1.21 2020/04/10 08:02:04 adam Exp $
 
-SHA1 (alembic-1.4.0.tar.gz) = 637491458046ceb122ac4f94e25fa70fa64a89cc
-RMD160 (alembic-1.4.0.tar.gz) = 66bde458f6d5f2e74506b9aeac75381aff1588e4
-SHA512 (alembic-1.4.0.tar.gz) = f66c17ce9bd1dedd74d0df6dbda569a2fceb7770ce1020730142c7bd3f72398c520c3b7fdb3a7af0494c231c8f323c01928ca3fcd867d4f7747ad3b5c1f8857c
-Size (alembic-1.4.0.tar.gz) = 1082449 bytes
+SHA1 (alembic-1.4.2.tar.gz) = 8967b6c2297d01372c2b10ccdaa1a2bf4d1ee523
+RMD160 (alembic-1.4.2.tar.gz) = 0f4f8cae20bf34a39a527b2d4d065a2c7478480b
+SHA512 (alembic-1.4.2.tar.gz) = 82bdfe442c19033aa2b802ec49edd13ed265c00a2b5a048490a83ffa8e53587c56a90b64d554e746a9189923419c528482cb7a7c950c210e0de47b32fa7c270e
+Size (alembic-1.4.2.tar.gz) = 1092045 bytes