Pourquoi ta requête Supabase s'arrête à exactement 1000 lignes (et ne te le dit jamais)
The article discusses a common issue with Supabase queries that stop returning results after 1000 rows without notifying the user. This limitation arises from the internal handling of PostgREST queries that lack an ORDER BY clause, which defaults to a physical tuple identifier and applies a row limit. The author suggests implementing a linting rule to enforce the inclusion of an ORDER BY clause in such queries to avoid this silent failure.
- ▪Supabase queries that do not specify an ORDER BY clause are limited to returning 1000 rows.
- ▪The limitation is due to the internal handling of PostgREST queries, which defaults to a physical tuple identifier.
- ▪The author recommends using a linting rule to ensure that all queries include an ORDER BY clause to prevent this issue.
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 Pourquoi ta requête Supabase s'arrête à exactement 1000 lignes (et ne te le dit jamais) #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)
