From: Mike Bayer Date: Sun, 5 Mar 2023 23:05:24 +0000 (-0500) Subject: changelog updates X-Git-Tag: rel_1_10_0~1 X-Git-Url: http://git.ipfire.org/gitweb/gitweb.cgi?a=commitdiff_plain;h=5563de380a032b711d9d3b062f4abc1690390d4a;p=thirdparty%2Fsqlalchemy%2Falembic.git changelog updates Change-Id: I2c796e4120a4674a46f4ebedbf63d9e40ebe49b9 --- diff --git a/docs/build/unreleased/1165.rst b/docs/build/unreleased/1165.rst index c2e3c9a8..b1dbf15d 100644 --- a/docs/build/unreleased/1165.rst +++ b/docs/build/unreleased/1165.rst @@ -3,10 +3,12 @@ :tickets: 1165 Fixed issue where indexes on SQLite which include SQL expressions would not - compare against themselves correctly, generating false positives. - SQLAlchemy as of version 2 has no support for reflecting expression based - indexes on SQLite; so for now, the behavior is that SQLite expression-based - indexes are ignored for autogenerate compare, in the same way that - PostgreSQL expression-based indexes were ignored for the time that - SQLAlchemy did not support reflection of such indexes (which is now - supported in SQLAlchemy 2.0 as well as this release of Alembic). + 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. + + diff --git a/docs/build/unreleased/index_updates.rst b/docs/build/unreleased/index_updates.rst index a468c737..c210069f 100644 --- a/docs/build/unreleased/index_updates.rst +++ b/docs/build/unreleased/index_updates.rst @@ -2,6 +2,7 @@ :tags: usecase, autogenerate, postgresql Added support for autogenerate comparison of indexes on PostgreSQL which - include SQL expressions; the previous warning that such indexes were - skipped is now removed. This functionality requires SQLAlchemy 2.0. - For older SQLAlchemy versions, these indexes are still skipped. + 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.