What ORMs Have Taught Me: Just Learn SQL (2014)

Re:What ORMs Have Taught Me: Just Learn SQL (2014) by eNTi on Wednesday October 21, 2020 @03:48AM (#24845641)

I'm currently in the process of porting api code from .net 3.2 soap where the code is a mixture of string based SQL queries and stored procedures to a .net core 3.1 webapi mvc + ef.

Let me tell you... readability and type saftey are a boons. Not a curse.

Things still get convoluted but boy the errors that can sneak into a complex sql statement are painful to debug.

As always the pendulum in this "article/rant" is swinging in the other direction ("everything was better in the past"). Also it's fricking (almost) 7 years old. That's a lifetime in software development.

[ Parent | on HN ]

Re:What ORMs Have Taught Me: Just Learn SQL (2014) by majewsky on Wednesday October 21, 2020 @04:33AM (#24845895)

> [7 years] is a lifetime in software development.

If we were talking about something like Kubernetes best practices, I'd definitely agree with this point. In this case, though, I don't see what substantially changed about ORMs or SQL in the last 7 years.

[ Parent | on HN ]

Re:What ORMs Have Taught Me: Just Learn SQL (2014) by ashtonian on Wednesday October 21, 2020 @04:15AM (#24845780)

The two are not mutually exclusive. Dapper provides types safety cleanly and imo is more readable than ef. Ef is heavy, requires trading to understand and is a giant pain if you need to implement performant sql.

[ Parent | on HN ]