Continuing on the work from #246, but this time applying the idea to the destroy callbacks.
With this fix, destroying an item in a list that has a unique DB constraint on the position column should not raise a DB error, as long as the sequential_updates option is enabled.
Continuing on the work from #246, but this time applying the idea to the
destroy
callbacks.With this fix, destroying an item in a list that has a unique DB constraint on the position column should not raise a DB error, as long as the
sequential_updates
option is enabled.Fixes #267