top | item 37506243 (no title) oldnet | 2 years ago Also you shouldn't give up access to your DB for security reasons.That's why API exists at first place. discuss order hn newest camgunz|2 years ago 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 yencabulator|2 years ago The architecture described in the article replicates the SQLite database on the page level. load replies (1) vbezhenar|2 years ago 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. berniedurfee|2 years ago No clients are trustworthy.
camgunz|2 years ago 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 yencabulator|2 years ago The architecture described in the article replicates the SQLite database on the page level. load replies (1)
yencabulator|2 years ago The architecture described in the article replicates the SQLite database on the page level. load replies (1)
vbezhenar|2 years ago 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. berniedurfee|2 years ago No clients are trustworthy.
camgunz|2 years ago
[0]: https://www.postgresql.org/docs/15/ddl-rowsecurity.html
yencabulator|2 years ago
vbezhenar|2 years ago
berniedurfee|2 years ago