pydantic-factories VS sqlmodel

Last but not least, we moved pydantic-factories from my GitHub namespace (Goldziher) into the starlite-api GitHub organization, so its now an official package of the org.

I'm the author and sole maintainer of a library called pydantic-factories.

You can see the docs here.

Here is the link: https://github.com/Goldziher/pydantic-factories

I'm glad to say pydantic-factories is now at v1.0.0 and includes support for pydantic v1.9.0+.

So - some of you perhaps read my previous post regarding pydantic-factories, but for those who didn't- its a python package that allows you to generate mock data for your pydantic models and dataclasses. It also works for vanilla python dataclasses, so its actually not only for pydantic.

looking at your badges - i don't care your "docs" pipeline is passing, what I am not seeing is test coverage. I suggest you checkout integrating sonar-cloud with your github repository. You can see how this looks here: https://github.com/Goldziher/pydantic-factories

Here is a link to the repository - https://github.com/Goldziher/pydantic-factories, I would of course love getting more stars. But I would especially love getting more users and contributors - really do feel free to add PRs, write issues and suggestions etc.

Seems like this is a known bug in SQLModel: https://github.com/tiangolo/sqlmodel/issues/10

I have not used it myself but the creator of fastapi has made https://github.com/tiangolo/sqlmodel

I have already posted this question in Stack Overflow and GitHub and have been ignored in both 😢. You guys are my last hope.

I had a requirement to process and validate large payloads of JSON concurrently for a web service, initially I implemented it using jsonschema and fastjsonschema but I found the whole JSON Schema Specification to be confusing at times and on top of that wanted better performance. Albeit there are ways to compile/cache the schema, I wanted to move away from the schema specification so I wrote a validation library inspired by the design of tiangolo/sqlmodel (type hints) to solve this problem easier.

Github Repository

I would say as long as your current solution works and is easy to maintain keep it. If you want to switch I would recommend FastAPI, it is new(ish), but definitely old enough to have been tested and used in a large variety of production usecases. In your case it might be interesting to have a look at SQLModel (works with FastAPI, same author), especially if the API endpoints match closely to the database objects. https://github.com/tiangolo/sqlmodel

SQLModel.

Sounds similar to https://github.com/tiangolo/sqlmodel

There was a lot of hype and excitement around the release of SQLModel, a Pydantic + SQLAlchemy hybrid Model library with native integration for FastAPI. I pulled it out just now and there hasn't been any update beyond the initial anouncment on August 25th.