feat: use uuid7 instead of uuid4 from now on #2309
Open
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.
UUID7 has the nice property of being semi-sequential, so it will be much nicer on DB indexes, and following that, improve query performance as well
Note we don't fully replace UUID4 everywhere: In tests, we don't care too much, so we don't build a UUID7 faker for those IDs, and in the Analytics module, we use UUID4 as a simple "random string" utility for generated identifiers (and using only the left few chars of it would break when using UUID7).