Closed lbialy closed 1 year ago
Thanks for this contribution. I think this scheme looks good to me. If a user chooses a database that doesn't support RETURNING (which is part of the SQL standard), they should know not to write such statements.
ok, resolving conflicts
@AugustNagro bump
This PR is mostly a proposal, hence limited testing. Currently it's not possible to write a custom returning scheme update because
.update
call does not allow it. This PR introduces this capability but it's not refined and probably lacks necessary genericity to work with all databases (that piece of handling is quite different from what I recall and see in Magnum's codebase anyway). A discussion on how to support this would be nice. Maybe it should be done the other way around - via extension methods forFrag
available in scopes ofDbType
subtype imports?