Hacker News Reader

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.

What? How does that ensure user 123 only generates LLM queries that constrain on rows where user=123?

As I wrote on the original thread, we recommend using the RDBMS row-level security features.

This blog discusses how to do that on Postgres

Way way too complicated. I thought this tool was suppsed to make my life easier

is there an easier way?

Yes write SQL

The question was around row level security