Bump sqlalchemy from 1.4.11 to 1.4.13

[dependabot]

Bumps sqlalchemy from 1.4.11 to 1.4.13.

Release notes

Sourced from sqlalchemy's releases.

1.4.13

Released: May 3, 2021

orm

• [orm] [bug] [regression] Fixed regression in selectinload loader strategy that would cause it to cache its internal state incorrectly when handling relationships that join across more than one column, such as when using a composite foreign key. The invalid caching would then cause other unrelated loader operations to fail.

  References: #6410

• [orm] [bug] [regression] Fixed regression where _orm.Query.filter_by() would not work if the lead entity were a SQL function or other expression derived from the primary entity in question, rather than a simple entity or column of that entity. Additionally, improved the behavior of _sql.Select.filter_by() overall to work with column expressions even in a non-ORM context.

  References: #6414

• [orm] [bug] [regression] Fixed regression where using _orm.selectinload() and _orm.subqueryload() to load a two-level-deep path would lead to an attribute error.

  References: #6419

• [orm] [bug] [regression] Fixed regression where using the _orm.noload() loader strategy in conjunction with a "dynamic" relationship would lead to an attribute error as the noload strategy would attempt to apply itself to the dynamic loader.

  References: #6420

engine

• [engine] [bug] [regression] Restored a legacy transactional behavior that was inadvertently removed from the _engine.Connection as it was never tested as a known use case in previous versions, where calling upon the _engine.Connection.begin_nested() method, when no transaction is present, does not create a SAVEPOINT at all and instead starts an outer transaction, returning a RootTransaction object instead of a NestedTransaction object. This RootTransaction then will emit a real COMMIT on the database connection when committed. Previously, the 2.0 style behavior was present in all cases that would autobegin a transaction but not commit it, which is a behavioral change.

... (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]

Superseded by #72.