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.
When users change their handles, that change doesnt necessarily propagate through the whole world consistently. The big issue this causes for us is if a user changes their handle from X to Y, and we arent able to validate it, we dont update our accounting of that change. Then if a new user creates an account with handle X, we fail to correctly initialize that user because of the uniqueness constraint.
I think I'll have to manually do these migrations, i doubt gorm will correctly swap the indexes from unique to not-unique.
I read through all the code referencing unique conflicts and handle setting and I believe this should work just fine.