News and Updates

SQLAlchemy 1.4.32 is now available.

Release 1.4.32 contains a fairly long series of fixes, quite a few in the area of correct error reporting for various error conditions. It also includes updates to accommodate changes in recent versions of cx_Oracle and mariadbconnector, as well as improvements to the test suite to correct for issues encountered within third party packaging and integration environments.

Development on SQLAlchemy 2.0 continues with recent emphasis on new typing-oriented mapping styles and overall pep-484 support throughout the whole library.

The complete changelog for 1.4.32 is at Changelog.

SQLAlchemy 1.4.32 is available on the Download Page.

SQLAlchemy 1.4.31 is now available.

Release 1.4.31 is an immediate fix to two regressions caused by 1.4.30, the first involving the PostgreSQL ARRAY datatype when used with ENUM contents, the second a regression in the asyncmy dialect which was missed by a broken CI configuration failing to test the dialect fully, where the removal of the pymysql dependency caused it to have a missing Binary symbol.

Thanks to the community for reporting these two regressions quickly and helping us get them fixed!

The complete changelog for 1.4.31 is at Changelog.

SQLAlchemy 1.4.31 is available on the Download Page.

SQLAlchemy 1.4.30 is now available.

Release 1.4.30 has a wide range of bug fixes and use case additions, affecting the ORM and Core components as well as the PostgreSQL and MySQL dialects. Overall, SQLAlchemy's main development is largely focused on the 2.0 release which is hoped to have beta releases in the coming months.

Thanks as always to our user community as well as our dedicated contributors for helping to make release 1.4.30 happen.

The complete changelog for 1.4.30 is at Changelog.

SQLAlchemy 1.4.30 is available on the Download Page.

SQLAlchemy 1.4.29 is now available.

Release 1.4.29 is released slightly ahead of schedule to accommodate for a fix for the mypy plugin, which stopped working as a result of a change released in mypy version 0.390, released earlier today. SQLAlchemy's continuous integration for mypy was inadvertently disabled which prevented this issue from being caught, which has been repaired.

Also included are fixes and use case additions for the ORM, asyncio, engine and MariaDB components.

Our user and contributor communities continue to deliver with bug reports, fixes and code contributions every day. Thanks much for their dedication and efforts.

The complete changelog for 1.4.29 is at Changelog.

SQLAlchemy 1.4.29 is available on the Download Page.

SQLAlchemy 1.4.28 is now available.

Release 1.4.28 adds new warnings emitted in the area of statement caching involving third-party datatypes, SQL constructs, and dialects, as user issues have revealed that the case of SQLAlchemy's new statement caching being disabled may be more common than was previously realized, and that this can also have a significant performance impact compared to release 1.3 in the area of ORM lazy loading. Previously, it was expected that 1.4 would be only modestly slower than 1.3 if statement caching were disabled, however ORM lazy loading and object refreshes, which occur on attribute access, can be an exception if these calls are very frequent.

For this reason, the new warnings will refer users to new documentation sections that describe the steps to take when these warnings occur.

As is always the case, huge thanks to our user and contributor communities as for their ongoing help and support as well as to our core team for their dedicated efforts and hard work.

The complete changelog for 1.4.28 is at Changelog.

SQLAlchemy 1.4.28 is available on the Download Page.