Fix: Increase calling_code column length to prevent truncation error #144
Conversation
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
|
Bump can this be merged in please |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes SQL truncation error during database seeding by increasing the calling_code column length from 10 to 30 characters.
The previous limit of 10 characters was insufficient for countries with multiple calling codes (e.g., Dominican Republic: "1-809, 1-829, 1-849" at 22 characters). The new limit of 30 characters accommodates all current
calling codes with room for future additions.
Error fixed (#143):
SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'calling_code' at row 1