updateSortingOrder for areas allows re-sorting in-place #293
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In response to problem noted here: OpenBeta/open-tacos#696 (comment)
In the end, I couldn't find a better way than resetting everything -1. I looked into seeing if Mongo supports deferred constraints to get it to check the uniqueness of
leftRightIndex
only after all the bulk updates are complete. I also looked into whether Mongo could update multiple documents atomically, to avoid the intermediate state where there is a duplicate index. Both didn't work out.