Bump sqlalchemy from 1.3.23 to 1.4.0

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

If you make any changes to it yourself then they will take precedence over the rebase.

---

Bumps sqlalchemy from 1.3.23 to 1.4.0.

Release notes

Sourced from sqlalchemy's releases.

1.4.0

Released: March 15, 2021

orm

• [orm] [bug] Removed very old warning that states that passive_deletes is not intended for many-to-one relationships. While it is likely that in many cases placing this parameter on a many-to-one relationship is not what was intended, there are use cases where delete cascade may want to be disallowed following from such a relationship.

  This change is also backported to: 1.3.24

  References: #5983

• [orm] [bug] Fixed issue where the process of joining two tables could fail if one of the tables had an unrelated, unresolvable foreign key constraint which would raise _exc.NoReferenceError within the join process, which nonetheless could be bypassed to allow the join to complete. The logic which tested the exception for significance within the process would make assumptions about the construct which would fail.

  This change is also backported to: 1.3.24

  References: #5952

• [orm] [bug] Fixed issue where the _mutable.MutableComposite construct could be placed into an invalid state when the parent object was already loaded, and then covered by a subsequent query, due to the composite properties' refresh handler replacing the object with a new one not handled by the mutable extension.

  This change is also backported to: 1.3.24

  References: #6001

• [orm] [bug] Fixed regression where the _orm.relationship.query_class parameter stopped being functional for "dynamic" relationships. The AppenderQuery remains dependent on the legacy _orm.Query class; users are encouraged to migrate from the use of "dynamic" relationships to using _orm.with_parent() instead.

  References: #5981

• [orm] [bug] [regression] Fixed regression where _orm.Query.join() would produce no effect if the query itself as well as the join target were against a _schema.Table object, rather than a mapped class. This was part of a more systemic issue where the legacy ORM query compiler would not be

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