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.
Case
discussion A have 3 posts with numbers : 1,2,3
discussion B have 2 posts with numbers : 1,2
with time order A1,A2,A3,B1,B2
then you "Delete Forever" post 2 at discussion A
discussion A have 2 posts with numbers : 1,3
discussion B have 2 posts with numbers : 1,2
with time order A1,A3,B1,B2
when you merge discussion B to A it "renumber"
B2 => A4
B1 => A3
A3 => A2
A1 => A1
but second sql update (B1 => A3) throws error that unique index A3 already exist
Changes proposed in this pull request:
we will fix posts number on target discussion before merging