I don’t think it’s a good idea to use SQLModel in a serious project. It’s not the best maintained because the only maintainer also maintains FastAPI, so SQLModel is sometimes left for quite a while without meaningful bugfixes.
I’d just use SQLAlchemy
Here is a bug fix where even a drug addict could see it’s merge worthy.
Could fall off the bar stool semi-conscious and still be able to acknowledge it’s merging worthy.
Just click the freak’n YES button.
Why market a package that is stuck in the WindowsXP era?
Great package, though the documentation on foreign keys could be a bit better in my opinion
Why single out lack of docs for foreign keys? The docs do deal with one to many and many to many relationships. Step by step.
The trick is finding that page. It’s there, just TOC is wonky. Unnecessarily hard to find things.
Foreign keys howto is a minor issue compared to the 70 PRs in the waiting queue.
Production? SQLModel is not production ready. I can name 70 reasons why not.
Please Sebastián bring on other maintainers with PR approval authority. Only this would be a game changer.
