3 ms·
Yeah, but this particular contract/API is pretty much "run arbitrary select/insert/update/delete statements" anyway! If you're using the postgrest language you
by lelanthran 4y ago
Yeah, but this particular contract/API is pretty much "run arbitrary select/insert/update/delete statements" anyway!
If you're using the postgrest language your options to stabilise the interface are minimal anyway, so why not just go with SQL and a whitelist?
- aljarry 4y agoYes, but the REST vs SQL forces a specific API for changes. REST - update/delete a specific record. SQL - update/delete based on a filter, or a query result. I can do `set a = b` for all rows in the table, which may be needed internally, but it's a pretty bad external interface.