Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I’m still in the think hard about the schema camp. I like to rely on the database to enforce constraints.


Yeah, a good database is pretty damn handy.

Have you had the pleasure of blowing young minds by revealing that production-grade databases come with fully fledged authnz systems that you can just...use right out of the box?


Can you say more? I’m interested.


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.


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.


I guess they mean something like Postgres' row-level security:

https://www.postgresql.org/docs/current/ddl-rowsecurity.html


Here's a vendor, but the underlying functionality is shipped with Postgresql server

https://supabase.com/docs/guides/database/postgres/row-level...




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: