Bump sqlalchemy from 1.3.20 to 1.3.23

Bumps sqlalchemy from 1.3.20 to 1.3.23.

Release notes

Sourced from sqlalchemy's releases.

1.3.23

Released: February 1, 2021

sql

• [sql] [bug] Fixed bug where making use of the TypeEngine.with_variant() method on a TypeDecorator type would fail to take into account the dialect-specific mappings in use, due to a rule in TypeDecorator that was instead attempting to check for chains of TypeDecorator instances.

  References: #5816

postgresql

• [postgresql] [bug] For SQLAlchemy 1.3 only, setup.py pins pg8000 to a version lower than 1.16.6. Version 1.16.6 and above is supported by SQLAlchemy 1.4. Pull request courtesy Giuseppe Lumia.

  References: #5645

• [postgresql] [bug] Fixed issue where using _schema.Table.to_metadata() (called _schema.Table.tometadata() in 1.3) in conjunction with a PostgreSQL _postgresql.ExcludeConstraint that made use of ad-hoc column expressions would fail to copy correctly.

  References: #5850

mysql

• [mysql] [usecase] Casting to FLOAT is now supported in MySQL >= (8, 0, 17) and MariaDb >= (10, 4, 5).

  References: #5808

• [mysql] [bug] [reflection] Fixed bug where MySQL server default reflection would fail for numeric values with a negation symbol present.

  References: #5860

• [mysql] [bug] Fixed long-lived bug in MySQL dialect where the maximum identifier length of 255 was too long for names of all types of constraints, not just indexes, all of which have a size limit of 64. As metadata naming conventions can create too-long names in this area, apply the limit to the identifier generator within the DDL compiler.

... (truncated)

Commits

• See full diff in compare view