* sql
  Fixed critical memory issue identified in cache key generation, where for very large and complex ORM statements that make use of lots of ORM
  aliases with subqueries, cache key generation could produce excessively large keys that were orders of magnitude bigger than the statement itself.
  Much thanks to Rollo Konig Brock for their very patient, long term help in finally identifying this issue.
  References: #8790
  * postgresql
  For the PostgreSQL and SQL Server dialects only, adjusted the compiler so that when rendering column expressions in the RETURNING clause,
  the “non anon” label that’s used in SELECT statements is suggested for SQL expression elements that generate a label; the primary example
  is a SQL function that may be emitting as part of the column’s type, where the label name should match the column’s name by default.
  This restores a not-well defined behavior that had changed in version 1.4.21 due to #6718, #6710. The Oracle dialect has a different RETURNING
  implementation and was not affected by this issue. Version 2.0 features an across the board change for its widely expanded support of RETURNING on other backends.
  References: #8770
  * oracle
  Fixed issue in the Oracle dialect where an INSERT statement that used insert(some_table).values(...).returning(some_table)
  against a full Table object at once would fail to execute, raising an exception.
  * tests
  Fixed issue where the --disable-asyncio parameter to the test suite would fail to not actually run greenlet tests and would also not prevent
  the suite from using a “wrapping” greenlet for the whole suite. This parameter now ensures that no greenlet or asyncio use will occur within the entire run when set.
  References: #8793
  Adjusted the test suite which tests the Mypy plugin to accommodate for changes in Mypy 0.990 regarding how it handles message output,
  which affect how sys.path is interpreted when determining if notes and errors should be printed for particular files.
  The change broke the test suite as the files within the test directory itself no longer produced messaging when run under the mypy API.
  * orm
  Fixed issue in joined eager loading where an assertion fail would occur with a particular combination of outer/inner
  joined eager loads, when eager loading across three mappers where the middle mapper was an inherited subclass mapper.
  References: #8738
  Fixed bug involving Select constructs, where combinations of Select.select_from() with Select.join(), as well as when using Select.join_from(),
  would cause the with_loader_criteria() feature as well as the IN criteria needed for single-table inheritance queries to not render,
  in cases where the columns clause of the query did not explicitly include the left-hand side entity of the JOIN.
  The correct entity is now transferred to the Join object that’s generated internally, so that the criteria against the left side entity is correctly added.

• Files Changed
• Browse Source

- Update to version 1.4.44:
  Change log is available
  https://docs.sqlalchemy.org/en/20/changelog/changelog_14.html#change-1.4.44
- Update to version 1.4.43: 
  Change log is available
  https://docs.sqlalchemy.org/en/20/changelog/changelog_14.html#change-1.4.43

• Files Changed
• Browse Source

• Browse Source