-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Environment:OS: Windows 10
node.js / npm versions:
Additional info:
-
Developer Tools
-
Not Needed
-
Iteration Jupiter
Problem Statement/Rationale
On the UI when I go to any mongo collection, I can sometimes browse pages forward even after I have ran out of documents. This seems to happen randomly, between different collections for me: some stop the pagination to the actual last page, some let me browse to one extra page, sometimes I've browsed even three empty pages after the actual mongo documents have run out. Although if I test only one collection, the pagination works consistently on it. Does MongoDB Compass remember deleted documents and the collection pagination adds them to the total amount of documents?
Steps to Reproduce
Hard to say, maybe have a collection of documents for two pages, delete enough documents to have one actual page and check if you can still navigate to page 2?
Expected Results
I expect to not be able to navigate to a page with no content.
Actual Results
I sometimes can navigate to a page with 0 collections.
- is duplicated by
-
COMPASS-8247 While paginating to next records, it is allowing use to move to next pages even I have scrolled to last page or last record, and showing more pages than actually it should be.
- Closed
-
COMPASS-8258 The next page button on the document view are clickable even after there is no document on the next pages
- Closed