1.10.0

Released: March 5, 2023

feature

[feature] [revisioning] Recursive traversal of revision files in a particular revision directory is
now supported, by indicating recursive_version_locations = true in
alembic.ini. Pull request courtesy ostr00000.
References: #760

[usecase] [autogenerate] [postgresql] Added support for autogenerate comparison of indexes on PostgreSQL which
include SQL expressions, when using SQLAlchemy 2.0; the previous warning
that such indexes were skipped are removed when the new functionality
is in use. When using SQLAlchemy versions prior to the 2.0 series,
the indexes continue to be skipped with a warning.

[bug] [autogenerate] Fixed issue in index detection where autogenerate change detection would
consider indexes with the same columns but with different order as equal,
while in general they are not equivalent in how a database will use them.
References: #1166
[bug] [autogenerate] [sqlite] Fixed issue where indexes on SQLite which include SQL expressions would not
compare correctly, generating false positives under autogenerate. These
indexes are now skipped, generating a warning, in the same way that
expression-based indexes on PostgreSQL are skipped and generate warnings
when SQLAlchemy 1.x installations are in use. Note that reflection of
SQLite expression-based indexes continues to not yet be supported under
SQLAlchemy 2.0, even though PostgreSQL expression-based indexes have now
been implemented.
References: #1165
[bug] [mssql] Properly escape constraint name on SQL Server when dropping
a column while specifying mssql_drop_default=True or
mssql_drop_check=True or mssql_drop_foreign_key=True.
References: #1187