2 ms·
While the OP was wrong on that, the problem I found is that Postgrest threw only slightly helpful errors when someone would try to access a column that they did
by CuriouslyC 3y ago
While the OP was wrong on that, the problem I found is that Postgrest threw only slightly helpful errors when someone would try to access a column that they didn't have permission to, rather than exclude that column from the result set and maybe throw a warning, which meant that you had to maintain multiple different versions of queries. This was a while ago, but coupled with my dislike of the query string syntax and some other stylistic choices I migrated to Hasura.
- throwaway11460 3y agoSo you have different queries per access level/role? Like userProducts, managerProducts, supportProducts, adminProducts...?
- CuriouslyC 2y agoYep, if the products table had columns that were only accessible to some users, SELECT * would throw an error in those cases.
- throwaway11460 2y agoIn my case I use Postgraphile. If you select a column that you can't access, you get an error - I don't see a problem there. PostgREST doesn't support column selection?
- SahAssar 2y agoIt does, but if you `SELECT *` and you don't have access to all the columns you will get an error. You need to select columns that you have access to and if you select all columns but don't have access to all columns you get an error. I think it's the same in Postgraphile, no?