refactor: use text for name column #570
Merged
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
reidsolon
changed the title
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.
This MR updates the name column in the personal_access_tokens table from string to text.
The current string limit (255 characters) causes SQL truncation errors when storing long user agent strings, especially from in-app browsers like Instagram.
Example error:
SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'name'Example user agent:
Mozilla/5.0 (Linux; Android 14; SM-0000E Build/UP1A.000005.007; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/138.0.0004.45 Mobile Safari/537.36 Instagram 000.0.0.00.00 Android (34/14; 450dpi; 1080x2116; samsung; SM-0006E; a55x; s5e0000; en_GB; 746325133