A general issue here is it'll break many existing PRs, but on the other hand: they're all breaking changes to column quoting/casing that can't be merged.

Overall for v3 I'm thinking of drastically changing the interface, maybe making it a base class where Insert<T> is what you implement...rather than the adapter. The adapters are just so brittle as so many issues have shown, and what people want to change on casing, etc. If they could be overridden directly, more easily scoped to each provider, PRs to fix one wouldn't break all others, etc. I need to write up ideas for .Contrib v3 (and general), but...yeah, minor brain dump there.

I'm fine with this as-is, given we can't merge the conflicting PRs anyhow. @mgravell thoughts?