Update temp table handler to support utf8mb4 if that is the db collation #15992
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.
Overview
Update temp table handler to support utf8mb4 if that is the db collation
Before
When temp tables are created using utf8 - the default & always the case AFAIK it is always utf8
After
If the DB is set to a default of UTF8MB4 (e.g as a result of running #15969 ) then that is respected
Technical Details
This is an alternate approach to @mfb's approach of trying to move the hard-coding to utf8mb4. When I looked at @mfb's excellent conversion script I realised he was changing the DB default & I started to think the right way to handle charset was to ensure the DB defaults were being set and only override them when we need to. This will only override if the default is not set
Comments