You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Medium (Affects functionality, but there is a workaround)
Additional Context (Optional)
The solution is easy. We should introduce a new ordering key besides -start_date, e.g. -id – just to be sure that the ordering is always the same, even in case of matching start dates of different entities.
The text was updated successfully, but these errors were encountered:
Page URL
https://go.ifrc.org/
Environment
Production
Browser
Firefox
Steps to Reproduce the Issue
Expected Behavior
Actual Behavior
The https://goadmin.ifrc.org/api/v2/appeal/?limit=5&offset=0&ordering=-start_date and
The https://goadmin.ifrc.org/api/v2/appeal/?limit=5&offset=5&ordering=-start_date query is not forced to use any other ordering entity, but the start date. In case of identical start date of 2 entities the query system can decide to have the same 2 entities in different order in the 1st and 2nd query, so an operation can disappear.
Priority
Medium (Affects functionality, but there is a workaround)
Additional Context (Optional)
The solution is easy. We should introduce a new ordering key besides -start_date, e.g. -id – just to be sure that the ordering is always the same, even in case of matching start dates of different entities.
The text was updated successfully, but these errors were encountered: