The archive API can return a rough estimate of the number of rows for queries that take too long. This is done to avoid saturating the DB with just count(*) calls.
However, this can be confusing and annoying for users.
Some possible fixes:
- The UI only shows the next page button if there are more results. Because the count can be inaccurate, there may be more results, but users have no way of finding out. This button should be shown regardless if there's a next page or not.
- The text showing the number of results should be changed to reflect that it's a rough estimate.
- Archive API pagination should be changed to include a field to signal if the count is an estimate or not. And based off this field we can show the appropriate messages.
The archive API can return a rough estimate of the number of rows for queries that take too long. This is done to avoid saturating the DB with just
count(*)calls.However, this can be confusing and annoying for users.
Some possible fixes: