Yep, we’re actively improving it based on user feedback, so thanks for that.
WRT to bytea, the REST endpoint just takes a query string that’s fed to Postgres. So, whatever works for INSERTs generally should work. I think you can do something like:
More details and options:
For prepared statements, unlike the DI API, there’s no state in which to build a query. Could your provide an example HTTP REST call to the query endpoint you’d ideally like to use for prepared statements?
The benefit of having bindings array separately from query_string is much better protection from SQL injection attack (i.e we don’t need to be very careful with escaping the inserted values), also much easier to understand what’s going on and debug.
?1 and ?2 syntax is not super important, plain “?” is enough.