While ORMs are great for simple CRUD with joins and stuff, they don't really support things like stored procedures, or even views all that wall. And if you have a code-first approach and want to have a procedure in your migration, you have to hand-write it.
While ORMs are great for simple CRUD with joins and stuff
So is plain SQL. Whenever stuff gets complex you hand-written SQL that is checked with the query planner is almost always better and easier to maintain than an ORM.
Secondly; ORMs get used as an excuse to not even look at the generated SQL anymore. In my 20 years experience as a Java dev, pretty much every implementation I came across suffered from thge N + 1
You're much better off using a simple object mapper togeter with plan SQL, or something like JOOQ IMHO.
-5
u/x6060x Sep 15 '20
I'm not sure if you are joking. Especially without the /s tag.