search

stac-utils / stac-fastapi-sqlalchemy

PostgreSQL backend for stac-fastapi using SQLAlchemy
MIT License
9 stars 10 forks source link

Bump sqlalchemy from 1.3.23 to 2.0.8 #5

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps sqlalchemy from 1.3.23 to 2.0.8.

Release notes

Sourced from sqlalchemy's releases.

2.0.8

Released: March 31, 2023

orm

  • [orm] [usecase] Exceptions such as TypeError and ValueError raised by Python dataclasses when making use of the _orm.MappedAsDataclass mixin class or _orm.registry.mapped_as_dataclass() decorator are now wrapped within an InvalidRequestError wrapper along with informative context about the error message, referring to the Python dataclasses documentation as the authoritative source of background information on the cause of the exception.

    References: #9563

  • [orm] [bug] Fixed issue in ORM Annotated Declarative where using a recursive type (e.g. using a nested Dict type) would result in a recursion overflow in the ORM's annotation resolution logic, even if this datatype were not necessary to map the column.

    References: #9553

  • [orm] [bug] Fixed issue where the _orm.mapped_column() construct would raise an internal error if used on a Declarative mixin and included the _orm.mapped_column.deferred parameter.

    References: #9550

  • [orm] [bug] Expanded the warning emitted when a plain _sql.column() object is present in a Declarative mapping to include any arbitrary SQL expression that is not declared within an appropriate property type such as _orm.column_property(), _orm.deferred(), etc. These attributes are otherwise not mapped at all and remain unchanged within the class dictionary. As it seems likely that such an expression is usually not what's intended, this case now warns for all such otherwise ignored expressions, rather than just the _sql.column() case.

    References: #9537

  • [orm] [bug] Fixed regression where accessing the expression value of a hybrid property on a class that was either unmapped or not-yet-mapped (such as calling upon it within a _orm.declared_attr() method) would raise an internal error, as an internal fetch for the parent class' mapper would fail and an instruction for this failure to be ignored were inadvertently removed in 2.0.

    References: #9519

... (truncated)

Commits


Dependabot compatibility score

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] commented 1 year ago

Superseded by #10.