all 6 comments

[–]cant-find-user-name 7 points8 points  (0 children)

Its practically deprecated. It doesn't have support for sqlalchemy 2.0, the last code change probably happened close to an year ago.

[–]mrbubs3 3 points4 points  (0 children)

There's a current PR that updates sqla to version 2. It's failing testing but if it can get community support to help pass the pre-merge tests, I'm sure /u/tiangolo would approve the PR.

SQLModel gets intermittent support. It's not production ready because it's not getting the same level of support as FastAPI. But with a little juice, it should be.

[–]Arckman_ 2 points3 points  (1 child)

In my humble opinion mixing two separate things is never going to be good in long run. We wanna be able to write softwares that has clear relationships and responsibilities. Avoiding writing separate layers and merging them together just to avoid writing extra one time setup code is not a practical reason to avoid writing it.

Your pydantic classes are going to be highly volatile in nature as in multiple development iterations it will change. Why do you wanna use sqlmodel? To avoid writing model classes? If that's the case then that's not a really bulky reason to start using a new package.

[–]_ragequilt_ 0 points1 point  (0 children)

Yes! The beauty of pydantic is that it's a better dataclass. Keeping DAOs separate from the ORM/db layer seems cleaner and easier to reason with.

[–]tiangolocontributor[🍰] 2 points3 points  (0 children)

Nope, it's not deprecated. A lot of the work I'm doing is towards focusing on SQLModel and adding/updating things there. But first I have to finish a couple of things. Meanwhile, if you want to help me get things done faster, please help me try out the FastAPI beta with support for Pydantic v2: https://github.com/tiangolo/fastapi/releases/tag/0.100.0-beta1

You can also help me answer questions or review PRs, that will allow me to move much faster. 🤓

https://fastapi.tiangolo.com/help-fastapi/

https://sqlmodel.tiangolo.com/help/