sqlmodel
SQL databases in Python, designed for simplicity, compatibility, and robustness. (by tiangolo)
geojson-pydantic
Pydantic data models for the GeoJSON spec (by developmentseed)
| sqlmodel | geojson-pydantic | |
|---|---|---|
| 23 | 1 | |
| 13,103 | 206 | |
| - | 2.4% | |
| 8.5 | 6.7 | |
| 2 days ago | 2 days ago | |
| Python | Python | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sqlmodel
Posts with mentions or reviews of sqlmodel.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-31.
-
SQLModel with the same relationship column twice
Seems like this is a known bug in SQLModel: https://github.com/tiangolo/sqlmodel/issues/10
-
Best ORM to use with FastAPI?
I have not used it myself but the creator of fastapi has made https://github.com/tiangolo/sqlmodel
-
SQLAlchemy: Parent instance is not bound to a Session; lazy load operation of attribute cannot proceed
I have already posted this question in Stack Overflow and GitHub and have been ignored in both 😢. You guys are my last hope.
-
I wrote okjson - A fast, simple, and pythonic JSON Schema Validator
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.
- Django Ninja – Fast Django REST Framework for Building APIs
-
Trending Python Projects of the Week
Github Repository
-
Tuesday Daily Thread: Advanced questions
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
-
The hand-picked selection of the best Python libraries released in 2021
SQLModel.
-
Pydbantic - A single model ( DB & Pydantic) with automatic migrations
Sounds similar to https://github.com/tiangolo/sqlmodel
-
tiangolo/SQLModel DoA?
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.
geojson-pydantic
Posts with mentions or reviews of geojson-pydantic.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-08-24.
-
SQLModel: SQL DBs based on Python type hints. The biggest thing I've built since FastAPI and Typer. 😅
All I would want from SQLModel right now would be support for a geography column from GeoALchemy and then a validator which converts the EWB to GeoJSON (https://geojson.org/) (As GeoJSON is a standard for most map frameworks to consume and produce spatial data). There is a Pydantic library representing the GeoJSON spec (https://github.com/developmentseed/geojson-pydantic) - it currently doesn't work in FastAPI since it uses tuples for coordinate sequences and Tuples are not supported until OpenAPI schema v3.1 AFAIK.
What are some alternatives?
When comparing sqlmodel and geojson-pydantic you can also consider the following projects:
pydantic-sqlalchemy - Tools to convert SQLAlchemy models to Pydantic models
fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production
pydantic - Data validation using Python type hints
SQLAlchemy - The Database Toolkit for Python
uvicorn-gunicorn-fastapi-docker - Docker image with Uvicorn managed by Gunicorn for high-performance FastAPI web applications in Python with performance auto-tuning.
ormar - python async orm with fastapi in mind and pydantic validation
FastAPIQuickCRUD - Generate CRUD methods in FastApi from an SQLAlchemy schema
sqlalchemy-hana - SQLAlchemy Dialect for SAP HANA
django-ninja - 💨 Fast, Async-ready, Openapi, type hints based framework for building APIs
datamodel-code-generator - Pydantic model and dataclasses.dataclass generator for easy conversion of JSON, OpenAPI, JSON Schema, and YAML data sources.
sqlalchemy-filters-plus - Lightweight library for providing filtering mechanism for your APIs using SQLAlchemy
sqlmodel vs pydantic-sqlalchemy
geojson-pydantic vs fastapi
sqlmodel vs pydantic
geojson-pydantic vs pydantic
sqlmodel vs SQLAlchemy
geojson-pydantic vs uvicorn-gunicorn-fastapi-docker
sqlmodel vs ormar
geojson-pydantic vs FastAPIQuickCRUD
sqlmodel vs sqlalchemy-hana
geojson-pydantic vs django-ninja
sqlmodel vs datamodel-code-generator
sqlmodel vs sqlalchemy-filters-plus