Why your Supabase query stops at exactly 1000 rows (and never tells you)
Supabase queries can silently stop returning results after 1000 rows due to an internal limit. This occurs when a query does not specify an ORDER BY clause, leading to a default sorting mechanism that can yield incomplete results. Developers are advised to implement linting rules to ensure that queries include an ORDER BY to avoid this issue.
- ▪Supabase applies a 1000-row limit on queries that do not include an ORDER BY clause.
- ▪The internal sorting mechanism can lead to unexpected results when the dataset exceeds 1000 rows.
- ▪Implementing linting rules can help developers avoid this silent failure in their queries.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3897818) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Michel Faure Posted on May 19 • Originally published at dev.to Why your Supabase query stops at exactly 1000 rows (and never tells you) #supabase #postgrest #postgres #eslint My ERP with Claude Code (29 Part Series) 1 How much are 91,000 lines produced with Claude Code actually worth? 2 Supabase RLS in production: four traps that silence your queries ... 25 more parts...
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
