upvote

points

by CharlieDigital8 hours ago |
comments
upvoteby gib4446 hours ago|
[-]
I meant code generators like sqlc
reply
upvoteby CharlieDigital6 hours ago|
parent|
[-]
Then this goes back to your question:

    > Is it good at the wrong thing?
No, it's good at the right thing which is allowing developers to write type-safe SQL queries using C# at the application layer versus writing SQL that gets translated into C#.
reply
upvoteby mattgreenrocks6 hours ago|
parent|
next
[-]
Yep, up there with ActiveRecord as the finest ORM I’ve ever used. What seals it for me is the low coupling it imposes on entities.
reply
upvoteby gib4444 hours ago|
parent|
prev|
[-]
I don't think you were aware of code gen SQL tools before this conversation right
reply
upvoteby CharlieDigital3 hours ago|
parent|
[-]
What's the relevance here? Some sort of weird "Ha! Gotcha!" I'm certainly aware of code to SQL and SQL to code generators as generalized techniques, but I've not used SQL to code generators because these are not practical for most teams in the domain spaces where I operate.

Your original quote, verbatim:

    > Eg compare to strongly-typed query generators
"strongly-typed query generators" not "strongly-typed command generators" nor "strongly-typed code generators".

EF is precisely a code to structured query language (SQL) query generator and not a query to code generator.

reply