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.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/michelfaure/why-your-supabase-query-stops-at-exactly-1000-rows-and-never-tells-you-4g57 |
| Publication time | Tue, 19 May 2026 07:56:11 +0000 |
| Retrieval time | 2026-05-19T08:04:57.437Z |
| Last seen | 2026-05-19T08:04:57.437Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | fPvO44YO1mh5 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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)
