this post was submitted on 08 Sep 2023
146 points (92.9% liked)

Programming

17508 readers
8 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
 

Some backend libraries let you write SQL queries as they are and deliver them to the database. They still handle making the connection, pooling, etc.

ORMs introduce a different API for making SQL queries, with the aim to make it easier. But I find them always subpar to SQL, and often times they miss advanced features (and sometimes not even those advanced).

It also means every time I use a ORM, I have to learn this ORM's API.

SQL is already a high level language abstracting inner workings of the database. So I find the promise of ease of use not to beat SQL. And I don't like abstracting an already high level abstraction.

Alright, I admit, there are a few advantages:

  • if I don't know SQL and don't plan on learning it, it is easier to learn a ORM
  • if I want better out of the box syntax highlighting (as SQL queries may be interpreted as pure strings)
  • if I want to use structures similar to my programming language (classes, functions, etc).

But ultimately I find these benefits far outweighed by the benefits of pure sql.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 23 points 1 year ago (1 children)

But then you get locked into the ORM's much more highly specific syntax.

At least the differences across SQL variants are not THAT major from my experience. The core use cases are almost the same.

[–] [email protected] 12 points 1 year ago* (last edited 1 year ago) (1 children)

How many good orm do you have per language? 1? 2? Orm is practically locked once one chooses the language

[–] [email protected] 4 points 1 year ago (1 children)

Surely there's more than 1 ORM that is at least used commonly enough to have a decent community for every major programming language. Just search the web for ORMs in python, JS, and Go and you'll see what I mean.

Not even language choice is forever. I've seen more codebases change languages or frameworks than I have seen changing databases.

What if you change jobs, and now work with a different language or framework? What if you're just helping out a sibling team in your company, and they use something different? Having to relearn a new ORM is annoying when you already know SQL.

I am not basing my argument on any of these things having a high likelihood of changing. The main point to me is that you're abstracting an already high level and very well abstracted API, and the reasons presented don't justify it (abstracting vendors but then locking you into a more specific vendor).

[–] [email protected] 3 points 1 year ago (1 children)

Sure, there are several. But, for instance, Python is pretty much only sqlalchemy. All others are not really common.

At the end with a single framework one can use several backends. That is pretty convient

[–] [email protected] 3 points 1 year ago

Sqlalchemy is really nice too, though I haven't used the 2.x series yet. I cannot stand the django ORM after using sqlalchemy.