Comments by "Brent Jacobs" (@br3nto) on "The Only Database Abstraction You Need | Prime Reacts" video.

  1. 19:20 he didn’t destroy the second half of the vid… all his points were surface level deep, but when you dive in with any rational thinking you realise his fears are based on misunderstandings of what ORMs really are and how they should be used.
    5
  2. 17:30 nooo… an ORM shouldn’t be chosen so you can switch database tech, instead chosen to be a client written in your language of choice to manage your persisted data. Just don’t use raw SQL in code. If the db schema changes, you’d have no IDE support to help you change all the places that may need changing. You and your team will likely get to a point where you’re fearful of changing the db schema, which is bad. The exception to this should be when you abstract the SQL behind a stored proc, the SQL of the stored proc should of course be managed by the migrations, and therefore should be in the code… but the calls to the stored proc should be done via an ORM.
    2
  3. 0:01 oh dude… ORMs aren’t trying to make SQL obsolete… this is gunna be painful. ORMs are no different from using a client written in your favourite language to speak to an API written in another language. So if you have a problem with ORMs, you have a problem with any type of system to system integration.
    2
  4. This guy is gonna freak out when people start building Object Prompt Model libraries to talk to LLMs. lol
    1
  5. 3:19 if you find you have fůcked up your db design, just throw in a migration and fix it… db schemas (and it’s ORM twin) aren’t static
    1
  6. 16:55 are you gonna raw dog calls to Redis, or your favourite pub/sub broker, or to HTTP clients/servers? No? Then you don’t need to raw dog SQL either. We don’t need to put databases on some magic pedestal and give it special treatment. They are just another way of persisting data.
    1
  7.  @ThePrimeTimeagen  sure, not by itself. I think it gets compelling when combined with my other counter-points.
    1
  8. 9:45 even when you write SQL you don’t know what the query plan will be unless you inspect that, so why is it a problem that you don’t know what the SQL will be unless you inspect it? Optimisation is maybe eventually needed whether you use SQL or an ORM, so it really doesn’t matter.
    1