Refactor user identification: Normalize user mapping and update messages table #57
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.
This PR refactors the user identification system to eliminate data redundancy and improve data integrity by normalizing the database schema as requested in the issue.
Changes Made
Database Schema Normalization
userstable withid(primary key),email(unique),name, andcreated_atcolumnsmessagestable to replace redundantuser_emailanduser_namecolumns with a singleuser_idforeign key0001_outgoing_venus.sql) to safely transform the existing schemaUser Management Logic
auth.tsto create or find users in the database during loginMessage System Updates
ws.ts) now usesuser_idinstead of storing duplicate user datamessages.ts) efficiently joins with users table to return user informationData Integrity Improvements
Before/After Comparison
Before:
After:
Testing
This normalization improves data integrity, reduces storage redundancy, and makes user management more efficient while maintaining full application functionality.
Fixes #56.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.