Bump sqlalchemy from 1.4.11 to 2.0.19

[dependabot]

Bumps sqlalchemy from 1.4.11 to 2.0.19.

Release notes

Sourced from sqlalchemy's releases.

2.0.19

Released: July 15, 2023

orm

• [orm] [bug] Fixed issue where setting a relationship collection directly, where an object in the new collection were already present, would not trigger a cascade event for that object, leading to it not being added to the _orm.Session if it were not already present. This is similar in nature to #6471 and is a more apparent issue due to the removal of cascade_backrefs in the 2.0 series. The _orm.AttributeEvents.append_wo_mutation() event added as part of #6471 is now also emitted for existing members of a collection that are present in a bulk set of that same collection.

  References: #10089

• [orm] [bug] Fixed issue where objects that were associated with an unloaded collection via backref, but were not merged into the _orm.Session due to the removal of cascade_backrefs in the 2.0 series, would not emit a warning that these objects were not being included in a flush, even though they were pending members of the collection; in other such cases, a warning is emitted when a collection being flushed contains non-attached objects which will be essentially discarded. The addition of the warning for backref-pending collection members establishes greater consistency with collections that may be present or non-present and possibly flushed or not flushed at different times based on different relationship loading strategies.

  References: #10090

• [orm] [bug] [regression] Fixed additional regression caused by #9805 where more aggressive propagation of the "ORM" flag on statements could lead to an internal attribute error when embedding an ORM Query construct that nonetheless contained no ORM entities within a Core SQL statement, in this case ORM-enabled UPDATE and DELETE statements.

  References: #10098

engine

• [engine] [bug] Renamed _result.Row.t and _result.Row.tuple() to _result.Row._t and _result.Row._tuple(); this is to suit the policy that all methods and pre-defined attributes on Row should be in the style of Python standard library namedtuple where all fixed names have a leading underscore, to avoid name conflicts with existing column names. The previous method/attribute is now deprecated and will

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