fix for mysql automatic column type with high field limit #13781
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.
Description
When using MySQL and creating a Plain Text field, if you set the Field Limit to a high value like 20,000 characters, the following error will be triggered:
This PR keeps the current behaviour for PostgreSQL and adjusts
PlainText::getContentColumnType()
to account for various MySQL limits to use text, medium text and long text columns.Related issues
support issue