TOTALLY! A lot of the answers here commit the original sin of think SQL = RDBMS. Expose the sql OF the rdbms is not ideal (security and all that), but none in

TOTALLY! A lot of the answers here commit the original sin of think SQL = RDBMS. Expose the sql OF the rdbms is not ideal (security and all that), but none in this world say SQL demand to be the one of the rdbms. You can create a SQL layer (alike GraphQL) that is "compiled" to calls that MAYBE are translated to a rdbms. MAYBE. If GraphQL is ok, sql is too.