Add column comment about case-sensitive tokens#14
Merged
dsquier merged 1 commit intodsquier:masterfrom Apr 22, 2020
ybelenko:12_access_token_collation
Merged
Add column comment about case-sensitive tokens#14dsquier merged 1 commit intodsquier:masterfrom ybelenko:12_access_token_collation
dsquier merged 1 commit intodsquier:masterfrom
ybelenko:12_access_token_collation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I've reconsidered. Force user to use specific
COLLATIONmight be a bad idea. This comment just notifies to set case-sensitiveCOLLATIONwhen tokens arebase58/base64encoded randoms.Even more important that I don't know which
COLLATIONto recommend. I've seenutf8mb4_bin, but not sure. 😄Closes #12