arangojs

We actually did the same for ArangoDB (I think we first did this in 2015, I remember being surprised nobody had done something similar for SQL at the time). Here's the JS driver's current implementation of it: https://github.com/arangodb/arangojs/blob/main/src/aql.ts#L1... Basically the `aql` template tag returns an object that can also be fed back into it and we also deduplicate arguments to avoid sending redundant data over the wire. There's also an escape hatch via a helper function (`aql.literal`) in cases where you need to insert literals that aren't known at compile time (e.g. you load query filters from a configuration file).

SQL actually demonstrates a good use case for custom template handlers. It's not SQL, but we're using a template handler to make writing parameterized queries trivial for ArangoDB: https://github.com/arangodb/arangojs#aql Example: var userCollection = db.collection('_users'); var role = 'admin'; db.query(aql` FOR user IN ${userCollection} FILTER user.role == ${role} RETURN user `) The template handler returns an object with the parameterized query string and the parameter values, which the `query` method understands. Because collection parameters are syntactically distinct from regular parameters this also avoids accidentally passing in arbitrary strings as collection names -- and of course it completely avoids injection attacks as a category. In my experience this is actually much more comfortable

You can use the Foxx framework to create a REST api that suits your needs. There is also a community project for an ORM, see https://github.com/arangodb/arangojs/issues/215 However, in general it is more flexible and safer to use Foxx, because it allows you to fine tune complexes queries and supports transactions.