Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bump sqlalchemy from 1.4.46 to 2.0.1 #738

Merged
merged 5 commits into from
Apr 5, 2023
Merged

Bump sqlalchemy from 1.4.46 to 2.0.1 #738

merged 5 commits into from
Apr 5, 2023

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 2, 2023 •
edited
Loading

Bumps sqlalchemy from 1.4.46 to 2.0.1.

Release notes

Sourced from sqlalchemy's releases.

2.0.1

Released: February 1, 2023

orm

  • [orm] [bug] [regression] Fixed regression where ORM models that used joined table inheritance with a composite foreign key would encounter an internal error in the mapper internals.

    References: #9164

  • [orm] [bug] Added support for PEP 484 NewType to be used in the _orm.registry.type_annotation_map as well as within Mapped constructs. These types will behave in the same way as custom subclasses of types right now; they must appear explicitly within the _orm.registry.type_annotation_map to be mapped.

    References: #9175

  • [orm] [bug] When using the MappedAsDataclass superclass, all classes within the hierarchy that are subclasses of this class will now be run through the @dataclasses.dataclass function whether or not they are actually mapped, so that non-ORM fields declared on non-mapped classes within the hierarchy will be used when mapped subclasses are turned into dataclasses. This behavior applies both to intermediary classes mapped with __abstract__ = True as well as to the user-defined declarative base itself, assuming MappedAsDataclass is present as a superclass for these classes.

    This allows non-mapped attributes such as InitVar declarations on superclasses to be used, without the need to run the @dataclasses.dataclass decorator explicitly on each non-mapped class. The new behavior is considered as correct as this is what the PEP 681 implementation expects when using a superclass to indicate dataclass behavior.

    References: #9179

  • [orm] [bug] Added support for PEP 586 Literal[] to be used in the _orm.registry.type_annotation_map as well as within Mapped constructs. To use custom types such as these, they must appear explicitly within the _orm.registry.type_annotation_map to be mapped. Pull request courtesy Frederik Aalund.

    As part of this change, the support for sqltypes.Enum in the _orm.registry.type_annotation_map has been expanded to include support for Literal[] types consisting of string values to be used, in addition to enum.Enum datatypes. If a Literal[] datatype

... (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 dependabot bot added the dependencies Pull requests that update a dependency file label Feb 2, 2023
@dependabot dependabot bot mentioned this pull request Feb 2, 2023
Closed
@dependabot dependabot bot force-pushed the dependabot/pip/sqlalchemy-2.0.1 branch from 2060b76 to 8f48efc Compare February 3, 2023 18:22
@sdjmchattie
Copy link
Contributor

Until the issue with Pandas .read_sql() is updated to work with SQLAlchemy 2.0, we cannot resolve the outstanding failing tests here.

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 7, 2023

A newer version of sqlalchemy exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

@sdjmchattie
Copy link
Contributor

Looks like Pandas will have a fix soon: pandas-dev/pandas#48576

They are currently on version 1.5.3. Not sure if this will make it into the next release or a later one. Will keep an eye out.

@amotl amotl mentioned this pull request Mar 13, 2023
Merged
5 tasks
@sdjmchattie
Copy link
Contributor

The release notes on Pandas GitHub page says that they are expecting to release Pandas 2.0.0 in about two weeks from now and that this will provide support for SQLAlchemy 2.0

@sdjmchattie
Copy link
Contributor

@dependabot rebase

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Apr 5, 2023

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

dependabot bot and others added 4 commits April 5, 2023 18:40
@dependabot @sdjmchattie
Bump sqlalchemy from 1.4.46 to 2.0.1
ee60145 
Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 1.4.46 to 2.0.1.
- [Release notes](https://github.com/sqlalchemy/sqlalchemy/releases)
- [Changelog](https://github.com/sqlalchemy/sqlalchemy/blob/main/CHANGES.rst)
- [Commits](https://github.com/sqlalchemy/sqlalchemy/commits)

---
updated-dependencies:
- dependency-name: sqlalchemy
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot @sdjmchattie
Bump sqlalchemy from 1.4.46 to 2.0.1
78d5bb4 
Bumps [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) from 1.4.46 to 2.0.1.
- [Release notes](https://github.com/sqlalchemy/sqlalchemy/releases)
- [Changelog](https://github.com/sqlalchemy/sqlalchemy/blob/main/CHANGES.rst)
- [Commits](https://github.com/sqlalchemy/sqlalchemy/commits)

---
updated-dependencies:
- dependency-name: sqlalchemy
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@sdjmchattie
Move the SQL engine bind to the reflect method call
b9049c7
@sdjmchattie
Use new SQLAlchemy CursorResult and MappingResult types
fd5851a 
The old default of returning a dict was deprecated in 1.4
@sdjmchattie sdjmchattie force-pushed the dependabot/pip/sqlalchemy-2.0.1 branch from b10d7af to b68b124 Compare April 5, 2023 17:42
@sdjmchattie sdjmchattie force-pushed the dependabot/pip/sqlalchemy-2.0.1 branch from b68b124 to 0e5fb70 Compare April 5, 2023 17:50
@sdjmchattie sdjmchattie merged commit 852f24a into develop Apr 5, 2023
@sdjmchattie sdjmchattie deleted the dependabot/pip/sqlalchemy-2.0.1 branch April 5, 2023 17:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@sdjmchattie