Sorting only sorts current list of 100

[nus-pe-bot]

Since the find function only finds the first 100 entries in the database, the filtering may cause minor to major inconvinience to users.

When I filter by sorting, I expect a sorting of all housing that should be eligible, instead of only those extracted to a list. This makes the sorting feature more useful. Basically, the scenario is that if I want to sort by lowest to begin with, chances are I want to view the cheapest houses within the entire database and not just within the list.

In the case of having all the expensive housing listed first in the database, there may be difficulty.

---

_{[original: nus-cs2113-AY2021S2/pe-interim#1329] [original labels: severity.Medium type.FeatureFlaw]}

[jadenwjh]

Team's Response

For this case, wouldn't the user add more filter parameters so that the number of houses to pull will be reduced? Consider how many houses there are in Singapore and the requirements when selecting a house, would it make sense for the user to not set filters and sort solely on price?

Duplicate status (if any):

--