Doctrine generated SQL unaffected by recipe dbal charset utf8mb4 #368
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.
Currently the yaml configuration in the doctrine recipe assigns the charset value to
utf8mb4
:But this does not affect the configuration of doctrine generated SQL as charset and collation of the tables don't inherit this default charset database value.
So SQL generated through
doctrine:schema:update --dump-sql
keeps addingDEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci
by table.This is true even if mysql server is configured to use utf8mb4 by default or
?charset=utf8mb4
is added toDATABASE_URL
env variable.IMHO it would be better to change the defaults for doctrine recipe so generated SQL really uses utf8mb4 by table.