41 ms·
There's a lot to like about the Django ORM. And Django still has it's place. What I'd like is a SQL that creates and consumes a JSON structure as output/input
by bb88 2y ago
There's a lot to like about the Django ORM. And Django still has it's place.
What I'd like is a SQL that creates and consumes a JSON structure as output/input, and then there wouldn't really be a need to serialize/deserialize anything. Python would be a lightweight wrapper for authentication, error handling, logging, and data processing that couldn't be easily done with SQL.
I mean people are trying this, but SQL feels so arcane. If you have tabular data and working with spreadsheets, SQL is great. And the JSON support in postgres is a badly bolted on design choice to force tree style data into tabular data.
Instead they should modify SQL to process tree style data as tree style data.
- eigenvalue 2y agoThere is a JSON column type in SQLite now, and it's supported by SQLModel/SQLalchemy: https://www.sqlite.org/json1.html https://www.sqlite.org/json1.html
- bb88 2y agoThere's a JSONB column type in postgres for a while now too with the arrow syntax. I think my point is that the structure of the data in a relational database is tree-like. Yet we can only get tabular data out of the queries.