[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.
[orm] [bug] Added support for PEP 484NewType 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.
[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.
[orm] [bug] Added support for PEP 586Literal[] 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
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)
Bumps sqlalchemy from 1.3.22 to 2.0.1.
Release notes
Sourced from sqlalchemy's releases.
... (truncated)
Commits
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)