Designing the most performant row-level security schema in Postgres (2018)

Re:Designing the most performant row-level security schema i... by MuffinFlavored on Friday February 14, 2020 @07:01PM (#22331730)

How frowned upon is it today to just do

``` const { accountId } = decodeJwt(req.headers.authorization) SELECT * FROM items WHERE account_id = :accountId ```

I get that it's about the exact opposite of what the article is trying to do but it looks a whole lot easier to maintain.

[ Parent | on HN ]

Re:Designing the most performant row-level security schema i... by wefarrell on Friday February 14, 2020 @10:04PM (#22332872)

The article is solving a much more complicate use case where items can be read by a list of users and written to by another list of users.

[ Parent | on HN ]

Re:Designing the most performant row-level security schema i... by tln on Friday February 14, 2020 @09:25PM (#22332701)

I wouldn't frown upon it, and would be surprised if the vast majority of apps didn't use app level segregation.

At some level of complexity SQL gets hard to migrate, upgrade, switch vendors and even cloud providers

[ Parent | on HN ]