Four Supabase bugs, one silent failure pattern: no errors, wrong data returned

A developer working on a Supabase-backed platform encountered four separate data incidents within a single week, each triggered by a different client reporting missing or incorrect records. The bugs spanned default function grants exposing anon access, conflicting ON DELETE and CHECK constraints, infinite RLS policy recursion, and an unordered query silently capped at 1,000 rows using ctid as a fallback sort. In every case, the database executed the query without raising an exception, returning HTTP 200 responses with quietly incorrect or incomplete payloads. No errors appeared in application logs or monitoring tools like Sentry, making diagnosis difficult and misdirected each time. Reviewing all four incidents together, the author identifies a shared failure mode: Supabase and Postgres silently delivering wrong results rather than surfacing detectable faults.