You have explicit control over transactions with functions https://postgrest.org/en/latest/references/api/functions.html https://postgrest.org/en/latest/referen

You have explicit control over transactions with functions https://postgrest.org/en/latest/references/api/functions.html https://postgrest.org/en/latest/references/api/functions.htm.... I think this sentiment stems from users of postgrest-js[1], which is a JS library that gives an ORM feel to PostgREST requests. Under that abstraction, users don't realize they're using a REST API, instead of a direct postgres connection. So in this case users are really asking for "client-side transactions"[2], which are not supported in PostgREST. [1]: https://github.com/supabase/postgrest-js https://github.com/supabase/postgrest-js [2]: https://github.com/PostgREST/postgrest/issues/286 https://github.com/PostgREST/postgrest/issues/286