Sorting can only happen on a single field, because this is a limitation by DataViews. However, if the sorting is not done on a unique value; the results may vary per request. E.g. The CsvDataSource has already shown in the unit tests that sort by age, where multiple actors have the same age, will not constantly create the same sorting.
To avoid this problem, we need to have a default secondary sorting on the ID. It doesn't matter if it is ASC or DESC (I would suggest using the same as the primary sorting), as long as it is applied. This will make sure the sorting is always the same, because the secondary field should always be unique.
Sorting can only happen on a single field, because this is a limitation by DataViews. However, if the sorting is not done on a unique value; the results may vary per request. E.g. The CsvDataSource has already shown in the unit tests that sort by age, where multiple actors have the same age, will not constantly create the same sorting.
To avoid this problem, we need to have a default secondary sorting on the ID. It doesn't matter if it is ASC or DESC (I would suggest using the same as the primary sorting), as long as it is applied. This will make sure the sorting is always the same, because the secondary field should always be unique.