Add short alphanumeric public_id from integer#15
Merged
Conversation
927311a to
328f4e2
Compare
Owner
Author
|
Updates needed:
|
Wanted the following properties: - source column is a integer (4 bytes) - public_id is a text (not char(5)), 1 byte per char - obfuscated enough so next value is not "guessable", pseudo random - reversible - Only PL/PgSQL functions, no extensions needed - Implementation is not math-heavy This seems to fit the bill and has these functions: - obfuscate_id(id INTEGER) - to_base62_fixed(val BIGINT, width INT DEFAULT 5) - from_base62_fixed(str TEXT) - deobfuscate_id(public_id CHAR(5)) For 5 chars we could do up to ~1 billion values For 6 chars we could do up to around 56 billion values
4a8fe8b to
7f2e831
Compare
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
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.
Wanted the following properties:
integer(4 bytes)public_id, 5 characters of length, regardless of length of integertext(notchar(5)per PostgreSQL "don't do this"), 1 byte per char, so 5 bytes for the charspublic_idcan be reversed into the original integer valueThis seems to fit the bill and has these functions:
For 5 char values, we could do up to ~1 billion values
For 6 char values, we could do up to ~56 billion values