Show HN: MЯO (ORM backwards) write SQL then generate its host-language wrapper
marketplace.visualstudio.com
marketplace.visualstudio.com
1. Utilize an abstraction to connect to the database or what connection string is used. For example, using AAD vs shared credentials when connecting to the DB.
2. Centered around Stored Procedures. I'd like to have everyone focused on creating the SP and then having the model created automatically from that SP.
Stored procedures are automatically supported. It's just SQL. We can discover the return type and create the wrapper just as we can for a query. But SQL in it's own file feels so much like stored procedures, you might prefer to store and version your SQL with your app code rather than create procedures that live in the database.
I bet this idea blows up - ORMs are such a PITA, and I love tools like Dapper that just wrap the contrapositive of this behavior - this seems even better to me.
Dapper has swept the world, but it still makes you maintain your own POCO, and your SQL is still in string literals, which has to be just the weirdest cultural practice. With my thing, because your SQL is in it's own file, we can constantly validate it, as you type, every time you save, every time you rebuild your queries, every time you run your tests.