ORM's vs raw SQL queries and when to use what?

Показать описание

In "ORM's vs raw SQL queries and when to use what?" I answer a programming question.

Рекомендации по теме

Комментарии

Lots of ORMs provide an API for writing raw queries as well which which allows you to combine both of best worlds. Danger that I see for new developers is that they might jump into ORMs too quickly and miss fundamental concepts like transactions for example

mikaknuuttila

Spent several hours looking into this topic today and then this vid shows up. Thanks for the insight!

GarmrZero

I have used Entity Framework extensively, and yes, there is a gain in to be made in terms of development time. However, these frameworks do not age very well. After a few years, incompatibilities start to appear if you don't run the latest and greatest of eveything coming with it. There are a lot of older version of databases running out there that eventually become incompatible with the latest version of the ORM. So just one thing to keep in mind.

lematindesmagiciens

I must confess I use raw quesries even for the most miniscule tasks. I am orm averse, I have a small utility class to process my raw queries easily.

kevinkkirimii

Great video Fred, the reason why I choose to use JOOQ over Hibernate in Java, you just cannot do joins efficiently in ORMs...

StyleTrick

Hey man you make a video regarding Internships(school) and how to get a part time software developer as a student.

jossyollarupuram

Yeah but I still way prefer raw SQL for everything. No magic. I know exactly what it's doing. It's faster. If I switch databases I can just copy paste the raw SQL and tweak it slightly for the new syntax to get it working again. New devs on the team don't need to learn a new ORM if they know SQL (which they SHOULD). I will never have to deal with debugging a stupid ORM that's just acting as the middleman between what I actually want to do.

You can also use the fastest drivers for your specific database and if you need to swap it out for C/C++ and make bindings for it if you really have a need for speed.

austecon

ORMs are so much quicker for one reason. Todays apps are fast dev cycles. No one has time for good stored procedures. What ends up happening is terrible stored procedures and or messy db layouts because of it. ORMS require less time to make very good SQL when you know how to use them correctly.

richie

Why in the bathtub? And why always your videos is in a senario walking?

rafaelaffonso

ORM's vs raw SQL queries and when to use what?

Raw SQL, SQL Query Builder, or ORM?

ORM's vs raw SQL queries and when to use what?

I tried 8 different Postgres ORMs

Why You SHOULDN'T Be Writing Raw SQL In 2023

SQL vs ORM - Which One To Choose For Database Interaction

Should you use an ORM? A query builder? Or raw SQL?

Django ORM - Performing raw SQL queries

DONT USE AN ORM | Prime Reacts

Eloquent vs Query Builder vs SQL: Performance Test

SQL vs Query Builders vs ORMs in TypeScript

ORM vs. SQL by Grzegorz Łuszczek

Everything You Need To Know About EF Core 8 Raw SQL Queries

Drizzle ORM in 100 Seconds

Secret To Optimizing SQL Queries - Understand The SQL Execution Order

I Would Never Use an ORM, by Matteo Collina

EF Core Raw SQL Queries Make Dapper Unnecessary #shorts

Django bypass ORM! - Performing raw SQL queries without the ORM

Raw SQL Queries in Python: Performance, Advantages, Challenges, and SQL Injection Prevention

Go SQL Comparison (squirrel, raw queries, sqlc and sqlx)

Are ORMs Worth Using?

Prisma, Eloquent, Doctrine: Why Use an ORM?

Why your DBA hates your ORM Hibernate or Entity application

DjangoCon 2018 - ORM: The Sequel

Rhythm Patel - No More Raw SQL: SQLAlchemy & ORMs | PyData London 2024