Is SQL model version maintained ? #1491
Replies: 3 comments 2 replies
-
No, it's not maintained anymore. That's why it's not documented anymore, but yes could add a callout on the README. As for mixing SQLAlchemy and SQLModel, I don't have any ready to use example, but since SQLModel is based on SQLAlchemy it should be fairly straightforward. |
Beta Was this translation helpful? Give feedback.
-
Thank you for the confirmation. I tried about an hour yesterday to make it work on SQL model for nothing ;) Reg the integration with sqlalchemy, I'm afraid I was not able to do it in about 90 minutes.
I'll try again for sure, but the documentation doesn't really help because too much is different from what's expected. Not saying tha sqlmodel is a good choice(I found your explanation for no official support pretty relevant) but as Fast API made the move fully, I find it hard to ignore that new wave for new comers to fastapi users like me. If you have some lead, it would be nice. And if I managed to have a proper configuration, I'll happily improve the documentation with your approval to reflect it. |
Beta Was this translation helpful? Give feedback.
-
PR to document the deprecation done: fastapi-users/fastapi-users-db-sqlmodel#27 |
Beta Was this translation helpful? Give feedback.
-
Hi,
Doesn't look the sqlmodel version is maintained. Looks like pydantic V1.
If no one maintains it, should it be written explicitly that the package is deprecated ?
And subsidiary question, would it be possible to provide an example on how to mix the sqlalchemy version of fastapi user with a modern fastapi, which will mostly be based on sqlmodel as it's the default choice(if not only) in the fast api doc.
Full example could include install by default + an example of foreign key between a sqlmodel object and a fastapi-user.
What's your input on that ?
Pierre
Beta Was this translation helpful? Give feedback.
All reactions