Silent Truncation: Why Your Supabase Queries Stop at 1000 Rows Without Warning

Supabase silently caps unordered queries at 1000 rows—a critical gotcha that only surfaces at production scale. Without explicit ORDER BY declarations, PostgREST applies an internal HTTP Range limit with no error messages or warnings, causing incomplete datasets to appear valid. Implementing structural linting rules is essential for preventing this class of silent data loss bugs.