Bump sqlalchemy from 1.4.25 to 1.4.26
Created by: dependabot[bot]
Bumps sqlalchemy from 1.4.25 to 1.4.26.
Release notes
Sourced from sqlalchemy's releases.
1.4.26
Released: October 19, 2021
orm
[orm] [bug] Improved the exception message generated when configuring a mapping with joined table inheritance where the two tables either have no foreign key relationships set up, or where they have multiple foreign key relationships set up. The message is now ORM specific and includes context that the
_orm.Mapper.inherit_condition
parameter may be needed particularly for the ambiguous foreign keys case.[orm] [bug] Fixed issue with
_orm.with_loader_criteria()
feature where ON criteria would not be added to a JOIN for a query of the formselect(A).join(B)
, stating a target while making use of an implicit ON clause.References: #7189
[orm] [bug] Fixed bug where the ORM "plugin", necessary for features such as
_orm.with_loader_criteria()
to work correctly, would not be applied to a_sql.select()
which queried from an ORM column expression if it made use of the_sql.ColumnElement.label()
modifier.References: #7205
[orm] [bug] Add missing methods added in #6991 to
_scoping.scoped_session
and_asyncio.async_scoped_session()
.References: #7103
[orm] [bug] An extra layer of warning messages has been added to the functionality of
_orm.Query.join()
and the ORM version of_sql.Select.join()
, where a few places where "automatic aliasing" continues to occur will now be called out as a pattern to avoid, mostly specific to the area of joined table inheritance where classes that share common base tables are being joined together without using explicit aliases. One case emits a legacy warning for a pattern that's not recommended, the other case is fully deprecated.The automatic aliasing within ORM join() which occurs for overlapping mapped tables does not work consistently with all APIs such as
_orm.contains_eager()
, and rather than continue to try to make these use cases work everywhere, replacing with a more user-explicit pattern is clearer, less prone to bugs and simplifies SQLAlchemy's internals further.The warnings include links to the errors.rst page where each pattern 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 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)