3 ms·
Also you shouldn't give up access to your DB for security reasons. That's why API exists at first place.
by oldnet 3y ago
Also you shouldn't give up access to your DB for security reasons.
That's why API exists at first place.
- vbezhenar 3y agoTechnically 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 3y agoNo clients are trustworthy.
- camgunz 3y agoPostgreSQL 9.5 (7.5 years old) shipped row-level security [0] which solves this. [0]: https://www.postgresql.org/docs/15/ddl-rowsecurity.html https://www.postgresql.org/docs/15/ddl-rowsecurity.html
- yencabulator 3y agoThe architecture described in the article replicates the SQLite database on the page level.
- camgunz 3y agoYeah but this thread became about "you need an API".