Currently, paginated querying of storage records does not take a custom ordering option, nor does it specify a default ordering in the SQL query being made. This means that DB shuffling or new records being added, can lead to duplicate or missing results across pages being returned. To resolve this, support for custom ordering should be added to the scan method.
Currently, paginated querying of storage records does not take a custom ordering option, nor does it specify a default ordering in the SQL query being made. This means that DB shuffling or new records being added, can lead to duplicate or missing results across pages being returned. To resolve this, support for custom ordering should be added to the scan method.