Enhance schema.sql with password column comments - #134
Open
Vinuthnainti wants to merge 1 commit into
Open
Conversation
Added comments to the password column for clarity on encoding format and future migrations.
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
1 participant
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.
Add documentation comments for the users.password column.
The column is defined as varchar(500), which may appear larger than necessary when storing encoded passwords. Added comments to clarify that the column stores Spring Security encoded password values and that the size helps accommodate different password encoding algorithms and future migrations without requiring schema changes.
Changes
Added inline documentation comments to the users.password column.
Clarified the rationale behind the column length.
Impact
Documentation-only change.
No schema modifications.
No functional changes.