:arrow_up: Bump sqlalchemy from 1.4.29 to 1.4.30

[dependabot[bot]]

Bumps sqlalchemy from 1.4.29 to 1.4.30.

Release notes

Sourced from sqlalchemy's releases.

1.4.30

Released: January 19, 2022

orm

• [orm] [bug] Fixed issue in joined-inheritance load of additional attributes functionality in deep multi-level inheritance where an intermediary table that contained no columns would not be included in the tables joined, instead linking those tables to their primary key identifiers. While this works fine, it nonetheless in 1.4 began producing the cartesian product compiler warning. The logic has been changed so that these intermediary tables are included regardless. While this does include additional tables in the query that are not technically necessary, this only occurs for the highly unusual case of deep 3+ level inheritance with intermediary tables that have no non primary key columns, potential performance impact is therefore expected to be negligible.

  References: #7507

• [orm] [bug] Fixed issue where calling upon _orm.registry.map_imperatively() more than once for the same class would produce an unexpected error, rather than an informative error that the target class is already mapped. This behavior differed from that of the _orm.mapper() function which does report an informative message already.

  References: #7579

• [orm] [bug] [asyncio] Added missing method _asyncio.AsyncSession.invalidate() to the _asyncio.AsyncSession class.

  References: #7524

• [orm] [bug] [regression] Fixed regression which appeared in 1.4.23 which could cause loader options to be mis-handled in some cases, in particular when using joined table inheritance in combination with the polymorphic_load="selectin" option as well as relationship lazy loading, leading to a TypeError.

  References: #7557

• [orm] [bug] [regression] Fixed ORM regression where calling the _orm.aliased() function against an existing _orm.aliased() construct would fail to produce correct SQL if the existing construct were against a fixed table. The fix allows that the original _orm.aliased() construct is disregarded if it were only against a table that's now being replaced. It also allows for correct behavior when constructing a _orm.aliased() without a selectable argument against a _orm.aliased() that's against a subuquery, to create an alias of that subquery (i.e. to change its name).

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

Superseded by #51.