⬆ Bump sqlalchemy from 2.0.23 to 2.0.26

[dependabot]

Bumps sqlalchemy from 2.0.23 to 2.0.26.

Release notes

Sourced from sqlalchemy's releases.

2.0.26

Released: February 11, 2024

orm

• [orm] [bug] Replaced the "loader depth is excessively deep" warning with a shorter message added to the caching badge within SQL logging, for those statements where the ORM disabled the cache due to a too-deep chain of loader options. The condition which this warning highlights is difficult to resolve and is generally just a limitation in the ORM's application of SQL caching. A future feature may include the ability to tune the threshold where caching is disabled, but for now the warning will no longer be a nuisance.

  References: #10896

• [orm] [bug] Fixed issue where it was not possible to use a type (such as an enum) within a _orm.Mapped container type if that type were declared locally within the class body. The scope of locals used for the eval now includes that of the class body itself. In addition, the expression within _orm.Mapped may also refer to the class name itself, if used as a string or with future annotations mode.

  References: #10899

• [orm] [bug] Fixed issue where using _orm.Session.delete() along with the _orm.Mapper.version_id_col feature would fail to use the correct version identifier in the case that an additional UPDATE were emitted against the target object as a result of the use of _orm.relationship.post_update on the object. The issue is similar to #10800 just fixed in version 2.0.25 for the case of updates alone.

  References: #10967

• [orm] [bug] Fixed issue where an assertion within the implementation for _orm.with_expression() would raise if a SQL expression that was not cacheable were used; this was a 2.0 regression since 1.4.

  References: #10990

examples

• [examples] [bug] Fixed regression in history_meta example where the use of _schema.MetaData.to_metadata() to make a copy of the history table would also copy indexes (which is a good thing), but causing naming conflicts indexes regardless of naming scheme used for those indexes. A "_history" suffix is now added to these indexes in the same way as is

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #120.