Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →In Supabase JavaScript, .limit(80) caps that query at 80 rows; it does not fetch the next rows automatically. If a site needs more matching articles, it must paginate and consume every page. That makes a hardcoded limit a plausible explanation for missing results—but the information available here does not prove it caused exactly 31 articles to disappear. The query, filters, response metadata, and database state are needed to establish the cause.
What .limit(80) does—and does not do
Supabase documents .limit(rows) as a maximum number of rows returned by a query. An explicit .limit(80) therefore caps that query’s result at 80 rows. It does not request additional rows after those 80.
As an Amazon Associate I earn from qualifying purchases.
The limit alone cannot explain why the reported shortfall was 31. That number depends on how many rows matched the query’s filters and on how the application handled the returned data. Other query limits, filters, joins, or application logic may also affect what the site displays. Without the actual query and response evidence, “one hardcoded limit” is a lead to investigate, not a confirmed root cause.
Free tools Windows power users keep installed
One-click scans. No signup required.
How to check whether the query returned a partial result
- Inspect the whole query chain. Find the
.limit(80)call and review the filters, joins, ordering, and any other client- or server-side caps applied to the request. - Compare matching rows with received rows. Check how many rows match under those exact filters, then compare that number with the array length your application received. PostgREST documents response range metadata and optional count preferences that can help identify how much of a result was returned: Pagination and Count.
- Check the order before using ranges. A stable order is important for repeatable pages. Supabase’s
.range(from, to)reference specifies zero-based, inclusive endpoints and notes that ranges respect query ordering. Use an order based on a stable field or combination of fields. - Verify that the application consumes every page. If the matching result exceeds one page, request successive ranges and stop when the result indicates there are no more rows. A query that fetches pages is not enough if the site only displays or stores the first response.
- Check the project-level maximum separately. Supabase’s versioned JavaScript v1 fetch documentation describes a configurable default maximum of 1,000 rows. That is distinct from an explicit client-side
.limit(80); confirm the deployed project setting and SDK version before relying on the versioned guidance.
Choosing a pagination approach
Supabase’s JavaScript range modifier and PostgREST’s limit/offset or range mechanisms can all divide a larger result into requests. The important differences are how page boundaries are expressed, how results are ordered, how the application detects the final page, and whether it checks a total count.
| Approach | Page boundaries | Ordering | Knowing when to stop |
|---|---|---|---|
Supabase JavaScript .range(from, to) |
Zero-based endpoints, with the ending index included. | Ranges follow query ordering; use a stable order. | Check the returned rows and, when useful, count information. |
| PostgREST limit/offset or range headers | Uses limit/offset query parameters or HTTP range headers. | Establish a stable order for repeatable page results. | Inspect response range metadata; a Prefer: count=exact request can ask for the total result size. |
PostgREST notes that exact counts can be slower on large tables, so requesting one on every query may carry a performance trade-off. Its pagination and count behavior is documented at PostgREST 16: Pagination and Count.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What the “31 articles vanished” claim establishes
The reported title describes 31 articles missing, no error or log, and a hardcoded .limit(80). Those details are not independently confirmed by the documentation, which establishes only the query and pagination behavior. To attribute the incident to the limit, the site’s actual query, matching-row count, response range or count information, and database state would need to support that explanation.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
