Re:"We ran out of columns" – The best, worst codebase
by scythmic_waves on Saturday August 03, 2024 @11:05AM
(#41146987)
Can you say more? I’m interested.
[ Parent
| on HN ]
Re:"We ran out of columns" – The best, worst codebase
by stavros on Saturday August 03, 2024 @11:10AM
(#41147024)
I guess they mean something like Postgres' row-level security:
https://www.postgresql.org/docs/current/ddl-rowsecurity.html
Re:"We ran out of columns" – The best, worst codebase
by Merad on Saturday August 03, 2024 @02:03PM
(#41148142)
Databases have pretty robust access controls to limit (a sql user's) access to tables, schemas, etc. Basic controls like being able to read but not write, and more advanced situations like being able to access data through a view or stored procedure without having direct access to the underlying tables.
Those features aren't used often in modern app development where one app owns the database and any external access is routed through an API. They were much more commonly used in old school apps enterprise apps where many different teams and apps would all directly access a single db.
Re:"We ran out of columns" – The best, worst codebase
by klysm on Monday August 05, 2024 @11:13PM
(#41167497)
I think supabase leans quite heavily into this, although I haven’t used it myself.
Row level security has been wonderful for multi tenancy in my experience though. I would highly recommend it.
Re:"We ran out of columns" – The best, worst codebase
by jaggederest on Saturday August 03, 2024 @06:41PM
(#41149837)
Here's a vendor, but the underlying functionality is shipped with Postgresql server
https://supabase.com/docs/guides/database/postgres/row-level...