3 ms·
Any number of database namespacing techniques already present in postgresql can prevent this. Link the user sign-on to a DB user and you’re gold.
by freeone3000 2y ago
Any number of database namespacing techniques already present in postgresql can prevent this. Link the user sign-on to a DB user and you’re gold.
- throwaway115 2y agoWhat? How does that ensure user 123 only generates LLM queries that constrain on rows where user=123?
- aazo11 2y agoAs I wrote on the original thread, we recommend using the RDBMS row-level security features. This blog discusses how to do that on Postgres https://www.2ndquadrant.com/en/blog/application-users-vs-row-level-security/ https://www.2ndquadrant.com/en/blog/application-users-vs-row...
- altdataseller 2y agoWay way too complicated. I thought this tool was suppsed to make my life easier
- saigal 2y agois there an easier way?
- altdataseller 2y agoYes write SQL
- saigal 2y agoThe question was around row level security
- deleted 2y ago[deleted]