Hacker News new | ask | show | jobs
by oldnet 1007 days ago
Also you shouldn't give up access to your DB for security reasons.

That's why API exists at first place.

2 comments

PostgreSQL 9.5 (7.5 years old) shipped row-level security [0] which solves this.

[0]: https://www.postgresql.org/docs/15/ddl-rowsecurity.html

The architecture described in the article replicates the SQLite database on the page level.
Yeah but this thread became about "you need an API".
Technically you can create different users with very precise access permissions. Might not be the good idea to provide that kind of API to the general public, but if your clients are trustworthy, it might work.
No clients are trustworthy.