Update sqlalchemy requirement from <2.0.5,>=1.4 to >=1.4,<2.0.6

[dependabot[bot]]

Updates the requirements on sqlalchemy to permit the latest version.

Release notes

Sourced from sqlalchemy's releases.

2.0.5.post1

Released: March 5, 2023

orm

• [orm] [bug] Added constructor arguments to the built-in mapping collection types including KeyFuncDict, _orm.attribute_keyed_dict(), _orm.column_keyed_dict() so that these dictionary types may be constructed in place given the data up front; this provides further compatibility with tools such as Python dataclasses .asdict() which relies upon invoking these classes directly as ordinary dictionary classes.

  References: #9418

• [orm] [bug] [regression] Fixed multiple regressions due to #8372, involving _orm.attribute_mapped_collection() (now called _orm.attribute_keyed_dict()).

  First, the collection was no longer usable with "key" attributes that were not themselves ordinary mapped attributes; attributes linked to descriptors and/or association proxy attributes have been fixed.

  Second, if an event or other operation needed access to the "key" in order to populate the dictionary from an mapped attribute that was not loaded, this also would raise an error inappropriately, rather than trying to load the attribute as was the behavior in 1.4. This is also fixed.

  For both cases, the behavior of #8372 has been expanded. #8372 introduced an error that raises when the derived key that would be used as a mapped dictionary key is effectively unassigned. In this change, a warning only is emitted if the effective value of the ".key" attribute is None, where it cannot be unambiguously determined if this None was intentional or not. None will be not supported as mapped collection dictionary keys going forward (as it typically refers to NULL which means "unknown"). Setting _orm.attribute_keyed_dict.ignore_unpopulated_attribute will now cause such None keys to be ignored as well.

  References: #9424

• [orm] [bug] Identified that the sqlite and mssql+pyodbc dialects are now compatible with the SQLAlchemy ORM's "versioned rows" feature, since SQLAlchemy now computes rowcount for a RETURNING statement in this specific case by counting the rows returned, rather than relying upon cursor.rowcount. In particular, the ORM versioned rows use case (documented at mapper_version_counter) should now be fully supported with the SQL Server pyodbc dialect.

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