Add a check for string-backed enum maximum length #776
Closed
jwpage wants to merge 2 commits into
Closed
Conversation
jwpage
marked this pull request as draft
July 15, 2026 00:20
Author
|
Needs further consideration |
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.
This adds a check for entity columns are mapped to a string-backed
enumTypeto ensure that the maximum length of the enum values does not exceed the defined database column length.(An additional future
enumTypecheck could be to ensure that integer-backedenumTypecolumns with negative numbers are not mapped to an unsigned integer, but I will leave that for a different PR.)