Skip to content

Bump sqlalchemy from 1.3.20 to 1.4.5

Norman Ziegner requested to merge dependabot/pip/sqlalchemy-1.4.5 into master

Bumps sqlalchemy from 1.3.20 to 1.4.5.

Release notes

Sourced from sqlalchemy's releases.

1.4.5

Released: April 2, 2021

orm

  • [orm] [bug] [regression] Fixed regression where the _orm.joinedload() loader strategy would not successfully joinedload to a mapper that is mapper against a CTE construct.

    References: #6172

  • [orm] [bug] [regression] Scaled back the warning message added in #5171 to not warn for overlapping columns in an inheritance scenario where a particular relationship is local to a subclass and therefore does not represent an overlap.

    References: #6171

sql

  • [sql] [bug] [postgresql] Fixed bug in new _functions.FunctionElement.render_derived() feature where column names rendered out explicitly in the alias SQL would not have proper quoting applied for case sensitive names and other non-alphanumeric names.

    References: #6183

  • [sql] [bug] [regression] Fixed regression where use of the Operators.in_() method with a _sql.Select object against a non-table-bound column would produce an AttributeError, or more generally using a _sql.ScalarSelect that has no datatype in a binary expression would produce invalid state.

    References: #6181

  • [sql] [bug] Added a new flag to the _engine.Dialect class called _engine.Dialect.supports_statement_cache. This flag now needs to be present directly on a dialect class in order for SQLAlchemy's query cache <sql_caching> to take effect for that dialect. The rationale is based on discovered issues such as #6173 revealing that dialects which hardcode literal values from the compiled statement, often the numerical parameters used for LIMIT / OFFSET, will not be compatible with caching until these dialects are revised to use the parameters present in the statement only. For third party dialects where this flag is not applied, the SQL logging will show the message "dialect does not support caching", indicating the dialect should seek to apply this flag once they have verified that no per-statement literal values are being rendered within the compilation phase.

... (truncated)

Commits

Merge request reports