Mariadb 10.2.7 null values change in information schema, #2817 #2824
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.
Since MariaDB 10.2.7,
information_schema.columns
now stores'null'
incolumn_default
instead ofnull
. MySQL 5.7 is not affected.This P/R should fix the two doctrine-related issues:
Not very used to doctrine, so please check and correct me if I'm wrong somewhere.
(see https://jira.mariadb.org/browse/MDEV-13132 and https://jira.mariadb.org/browse/MDEV-13341)