SQLAlchemy

“SQLAlchemy has an eDSL of SQL, so you can skip the whole ORM/table mapping layer”

“at no point were we married to it, you could generate your query any which way you please”

“As a user I just don't have to deal with most of its complexity on a day to day basis”

“It gives you a lot in return.”

“you realize you needed SQLA or some similar piece of tech all along”

“get rid of all of my workarounds that add or remove”

“make SQL more reusable/composable”

“sqlalchemy and alembic is a great toolchain outside of django”

“I once tried using SqlAlchemy but I couldn't help asking myself why it felt so complicated compared to Django.”

“SQLAlchemy vs hand rolled SQL and mapping the results it’s not even close.”

“they are both there for you for your highs (select * from table order by created at) and your lows”

“Yeah, you can use SQLAlchemy like this. It's called the data mapper pattern.”

“I am 100% sure what SQL do I want it to produce and what SQL will a particular ORM invocation produce.”

“I do use a very small subset of SQLAlchemy (the bits I understand) in data pipelines.”

“What function signature isn't going to look messy with 36 keyword arguments.”

“It's probably hard to come up with something messier than SqlAlchemy here.”

“So many things just don't really work in this world, like old-school lazy fetching in SQLAlchemy.”

“The main value I get from sqlalchemy is parsing the result into useful structures.”

“You don't need an ORM for any of that, just a query builder.”

“i've bounced between django and sqlalchemy”

“With SQLAlchemy approach I can easily find all usages of a particular column everywhere.”

“I insist on using SQLAlchemy for db models”

“Alchemy's strong point is "here's an existing database; let users who grok DB theory query it as efficiently and ergonomically as possible."”

“Lol I never knew django orm is faster than SQLAlchemy. But having used both that makes sense.”

“I can guarantee that someone equipped with a good foundation in SQL will be more successful debugging a Sequelize based application, than someone who has relied on SQLAlchemy”

“Every time I use them I think to myself it would be easier to just write SQL myself”

“Alchemy is the greatest thing in the world when you need its exact features.”

“sqlalchemy is better in every possible way”

“it started as an sql alchemy and pandas service”

“they're always lazy, so you never really know when the N+1s are going to happen”

“Sqlalchemy is a good example.”

“SQLAlchemy is undeniably the superior and far more capable ORM”

“the ORM blows SQLAlchemy out of the water, in terms of being able to produce quality software, quickly”

“I end up with a little more boilerplate”

“undisciplined (in terms of perf and cost) new ORM code being deployed (SQLAlchemy)”

“kludgy as it tries to translate SQL into a new language”

“I prefer a Django-like ORM to SQLAlchemy in spite of all the praises it gets”

“The SQLAlchemy integration looks interesting, but at the same time super specific.”

“SQL alchemy seems to be getting better.”

“I would still pick FastAPI/SQLAlchemy over Express and PostHog.”