]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
once again note pydantic is never really going to work
authorMike Bayer <mike_mp@zzzcomputing.com>
Mon, 5 Jun 2023 16:26:43 +0000 (12:26 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Mon, 5 Jun 2023 16:26:43 +0000 (12:26 -0400)
commitd7469c98fa7fce55a4ac123c8b12d4907af41d1b
tree94368e6efae247551af4c0e8f508ef43d86b0944
parent7f55ba3e08e2c2631c062550a4211309b2b9e238
once again note pydantic is never really going to work

In #9894 we see that pydantic's dataclass feature is doing an
end run around SQLAlchemy's collection mechanics that can't
be fixed without special steps, which we would surmise
is what SQLModel is doing here:

https://github.com/tiangolo/sqlmodel/blob/43a689d369f52b72aac60efd71111aba7d84714d/sqlmodel/main.py#L507

We don't do that, so note that we really are not supporting pydantic
directly; use SQLModel which was designed to resolve these issues.

Change-Id: I3e35e108546022c83d6c0ae73e32432cdc75d325
doc/build/orm/dataclasses.rst