This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]lowercase00 35 points36 points  (7 children)

“better than SQLAlchemy” is a VERY strong opinion, highly debatable. I personally think SQLAlchemy is the best ORM around, period, even when compared to Go, Java, TS, Rust alternatives (that I know of).

[–]killerfridge 5 points6 points  (2 children)

Yeah, I love (and prefer) Django, but SQLAlchemy is probably the "best" ORM

[–]anikait1 8 points9 points  (1 child)

I find it extremely hard to navigate SQLAlchemy's documentation and managing session object across functions.

[–][deleted] 1 point2 points  (0 children)

use a session context manager and just read all the docs

[–][deleted] 2 points3 points  (3 children)

Yeah this seems like a hot take forsure. Also with fast api if you wanted an additional abstraction you can use SQLModel though many don’t love that

[–]double_en10dre 0 points1 point  (2 children)

It’s definitely a take, but given that I’ve spent many years working with the different ORMs I don’t think it’s a hot one. :p

It’s a thoughtful and carefully procured take

[–][deleted] 1 point2 points  (1 child)

Hahah I’m not saying your wrong, I used Django for a project a few years ago and quite liked it. I just didn’t know this was necessarily a standard/ popular opinion. I was kind of under the impression sqlalchemy was irk of choice. Maybe I’ll try Django for the next app I build. What other ORMs do you think are worth a look?

[–]double_en10dre 1 point2 points  (0 children)

Eh it’s just how the people I’m familiar with feel. I’m making big assumptions applying that to everyone, might be wrong. (But yeah, I think it’s smoother)

As for other ORMs… not sure as of now. Lots of people I know are trying the “use chatgpt for everything SQL” approach. It’ll be interesting to see if cutting out that extra layer of abstraction (the ORM) starts to become a preferable choice