Cool idea, I've always wondered what it would look like to build a relatively large DB heavy stack where you use only standard SQL. I like the concept of being able to switch out DBs if you want to run it in different contexts (maybe SQL lite for local dev etc) and all your migrations etc would just work out of the box.

But I mean, that would probably be sort of a nightmare to make happen in practise. You'd need everyone that touches the code base to understand and accept that constraint, you'd probably be leaving a bunch of performance on the table without using DB specific features and it would drastically increase the test surface I suppose.

It's just a thought, I've never come across a situation where this would be worth doing over just sticking to a single provider but I'm interested to know if there are.

Also heads up, I tried to use the codapi C# playground and just get a "code execution timeout" every time. :)