search

Weasyl / weasyl

The website.
https://www.weasyl.com
Apache License 2.0
117 stars 30 forks source link

Bump sqlalchemy from 1.4.45 to 2.0.6 in /etc #1328

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps sqlalchemy from 1.4.45 to 2.0.6.

Release notes

Sourced from sqlalchemy's releases.

2.0.6

Released: March 13, 2023

orm

  • [orm] [bug] Fixed bug where the "active history" feature was not fully implemented for composite attributes, making it impossible to receive events that included the "old" value. This seems to have been the case with older SQLAlchemy versions as well, where "active_history" would be propagated to the underlying column-based attributes, but an event handler listening to the composite attribute itself would not be given the "old" value being replaced, even if the composite() were set up with active_history=True.

    Additionally, fixed a regression that's local to 2.0 which disallowed active_history on composite from being assigned to the impl with attr.impl.active_history=True.

    References: #9460

  • [orm] [bug] Fixed regression involving pickling of Python rows between the cython and pure Python implementations of Row, which occurred as part of refactoring code for version 2.0 with typing. A particular constant were turned into a string based Enum for the pure Python version of Row whereas the cython version continued to use an integer constant, leading to deserialization failures.

    References: #9418

sql

  • [sql] [bug] [regression] Fixed regression where the fix for #8098, which was released in the 1.4 series and provided a layer of concurrency-safe checks for the lambda SQL API, included additional fixes in the patch that failed to be applied to the main branch. These additional fixes have been applied.

    References: #9461

  • [sql] [bug] Fixed regression where the _sql.select() construct would not be able to render if it were given no columns and then used in the context of an EXISTS, raising an internal exception instead. While an empty "SELECT" is not typically valid SQL, in the context of EXISTS databases such as PostgreSQL allow it, and in any case the condition now no longer raises an internal exception.

    References: #9440

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