Bugfix/mysqltext #212
Merged
Bugfix/mysqltext #212
Conversation
This file contains 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
JFriel
approved these changes
Aug 16, 2023
|
@JFriel Theoretically yes - fortunately in this case the only installation affected is HIC's own PODMAN, where logging is space constrained anyway, so not an issue. |
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.
MySQL translation incorrectly uses TEXT type columns (64k limit) instead of LONGTEXT. Fixed in this PR, along with a typo and incorrect column length limit values for tinytext/text/mediumtext/longtext types.
Also cleans some whitespace, so best reviewed filtering that out: https://github.com/HicServices/FAnsiSql/pull/212/files?diff=unified&w=1