feat: add email_hash column for indexed user email lookup#130
Merged
Conversation
v0l
commented
Jun 15, 2026
Contributor
- Add email_hash BINARY(32) column with index to users table
- Add email_hash() utility using SHA-256 of lowercased+trimmed email
- update_user() automatically computes and stores email_hash
- Add GET /api/admin/v1/users/by-email endpoint using indexed lookup
- Add data migration to backfill email_hash for existing users at startup
- Add email_hash BINARY(32) column with index to users table - Add email_hash() utility using SHA-256 of lowercased+trimmed email - update_user() automatically computes and stores email_hash - Add GET /api/admin/v1/users/by-email endpoint using indexed lookup - Add data migration to backfill email_hash for existing users at startup
63810cb to
ee7b6ce
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.