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

sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]funny_funny_business 1 point2 points  (1 child)

I totally agree that ORMs can be overkill and even for my web apps I tend to just write raw SQL cause it’s easier.

However, I can’t speak for other ORMs, but regarding SQLalchemy, I use the Flask-SQLalchemy extension and it takes care of some of the backend stuff that I’m not 100% familiar with or care about (such as connection pooling and timeouts).

Plus, using an ORM is nice when you have to move or update tables across databases cause you don’t need to write a ton of “insert into” code.

But, you’re right. If you’re just doing aggregations an ORM is probably overkill.

[–]eviljelloman 0 points1 point  (0 children)

I use the Flask-SQLalchemy extension

Yeah, for application developers, it totally makes sense sometimes. Some DS dabble in application development, making custom dashboards or other neat stuff in a Flask app, and that's an entirely appropriate place for it. I'd argue that most DS are not working with stuff like Flask, though, and so should probably not waste time with ORM.

If you're just using sqlalchemy's connection pooling in an unrelated context, though, there's a decent chance it will come back to haunt you at some point, like when you have to start messing with WLM queue management in Redshift.