The WHERE clause you have to remember on every query

Short summary

When AI copilots generate SQL for multi-tenant analytics, the WHERE clause isolating customer data becomes the model's responsibility on every query—a silent data-leak risk when it fails. The author argues tenant isolation should be enforced at the interface level, not re-implemented per query or per surface, so no consumer—dashboard, API, or AI—can forget the filter. The post traces a progression from app-level filters through database row-level security to embedded dashboard tools, showing how each layer gets bypassed by the next consumer.

• •AI-generated SQL inherits the tenant-isolation burden from hand-written queries but without human review
• •Per-surface isolation (app filters, session variables, locked embed params) fails when a new consumer like a copilot composes its own queries
• •Isolation belongs at the interface contract, enforced by the runtime, so no caller can forget the filter

Generated with AI, which can make mistakes.