3 ms·
> no one in their right mind is going to expose their database to untrusted users in the first place I've seen projects do exactly this, with PostgreSQL row-le
by paulddraper 3y ago
> no one in their right mind is going to expose their database to untrusted users in the first place
I've seen projects do exactly this, with PostgreSQL row-level security.
https://www.graphile.org/postgraphile/ https://www.graphile.org/postgraphile/
EDIT: Though to be clear, it does seem a terrible idea to me too....even when you prevent unauthorized access, there is always the issue of resource usage.
- tacone 3y agoAlso Hasura and PostgREST (thus by extension Supabase). I would also add that one of the entry barriers of such projects is the need to write UDF. Most developers are not used to write UDFs, and the languagea (plsql and likes) themselves lack the features and ease of modern languages and vary among database vendors. As mentioned by other people there have been attempts to allow writing UDF using the JVM, Javascript, Python and so on, by they never caught on (and some of them are difficult to install) and are not that portable to other database vendors, they require installing third party extensions and so on. I for one see WASM to be a good candidate for a really portable solution.
- semiquaver 3y agoApologies, I should have said something more like “exposing the database to untrusted users is a specific and narrow use case that needs way more db-specific planning”. RLS is really cool tech but you need to design your schema and application around it for it to be useful. Slapping some WASM on any existing databases (especially the vast majority which have nothing like the unique capabilities provided by RLS) isn’t going to buy anything that doesn’t exist already.