I think I get why Cloudflare's CTO is asking this question. personally started using Django for backend development, boy, that thing is robust and cool, esp...

you are viewing a single comment's thread
view the rest of the comments

[–] phutatorius@lemmy.zip 2 points 2 months ago* (last edited 2 months ago) (1 children)

There is simply nothing better in my opinion.

Possibly SQLalchemy? But yeah, it's quite good, and there are ways you can bypass the Django ORM and write your own SQL in the cases where it's suboptimal. I've only had to do that a very small number of times during the 20-plus years I've been using Django (I was an early adopter, left Zope like a .38 round leaves a gun).

It also helps that I have some decent SQL optimization skills: when I was doing consulting, I triggered the resignations of two client DBAs because they insisted that there was no way to significantly improve a query's performance, then I did it. Stupid hill to die on, all they had to have done was to have said "OK, let's prototype it and see" instead of getting all dogmatic about it. Ego's a dangerous thing in software development.

[–] onlinepersona@programming.dev 2 points 2 months ago (1 children)

SQLalchemy is horrible, IMO. You have to read so much of its documentation to get a grip on things. And the backwards compatible changes they made while moving to (I think) SQLAlchemy2 make it terribly difficult to tell apart the API. And type hints were an abomination to deal with when they tried adding them (it's better now).

And don't get me started on migrations with alembic.

I wish the Django ORM could be extracted from Django and used in other projects, but then I also just want to go back to Django.

[–] logging_strict@programming.dev 1 points 1 month ago* (last edited 1 month ago)

Reply to /u/onlinepersona SQLAlchemy crocodile tears.

Really need a layer between SQLAlchemy and FastAPI (or litestar, ...). Otherwise would be messing around with SQLAlchemy/alembic internals for years. SQLAlchemy is an incredible time sink without that additional layer.

Created just such a package just never got around to publishing it:

static type checking throughout
sync and async support throughout
alembic support (both async and sync)
multiple databases. One per config file!
model built from dotted path of (sqlmodel and sqla mixins) components module
UDF (user defined functions)
database settings (PRAGMA, SHOW, SET, ...)
sqlite-[pysqlite|sqlcipher|aiosqlite] and postgresql-[psycopg2|asyncpg] supported
config does not store the password

Issues:

retire sqlite-sqlcipher PRAGMA rekey and key. Password in config unsafe
authentication by pulling from a password manager not implemented
strict validation of postgresql SHOW/SET keys incomplete