dbcheck does not properly check null values with mariadb 10.3

[jwlogemann]

A brief description of the issue goes here.

On a clean install of Bolt it keeps complaining about the database tables being out of date. Running the "update DB" command does nothing. Running the suggested SQL directly on the DB does nothing either (suggested structure is the same as the actual structure).

Details

Looking at the proposed changes they're all like this:
changedColumns: array:6 [▼
"user_id" => ColumnDiff {#2429 ▼
+oldColumnName: "user_id"
+column: Column {#1523 ▼
#_default: null
}
+changedProperties: array:1 [▼
0 => "default"
]
+fromColumn: Column {#2120 ▼
#_default: "NULL"
}
}

As you can see it wishes to changes the default from null to "NULL". Probably some change in how MariaDB 10.3 reports datatypes.

Question	Answer
Relevant Bolt Version	3.6
Install type	Composer install
BC Break	no
PHP version	7.2
Web server	Nginx, version [ 1.14.2]
For UX/UI issues	Browser name and version

Reproduction

If you're filing a bug, please describe how to reproduce it. Include as much
relevant information as possible, such as:

Bug summary

Install Bolt with a MariaDB 10.3 database

Specifics

Bug can be seen when accessing the backend

Steps to reproduce

Install Bolt

Expected result

I expect the database schema to be correct, and Bolt not to show any warnings

Actual result

Bolt shows a message to update the DB structure

[JarJak]

Could you check if MariaDB 10.2 gives same result?
See #7477 and doctrine/dbal#3189

[bobdenotter]

Also, be sure to run composer update, manually.. Depending on which kind of “composer install” you did, you might have older Doctrine components, because of Bolt’s compatibility with PHP 5.5.9.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Maybe this issue has been fixed in a recent release, or perhaps it is not affecting a lot of people?
It will be closed if no further activity occurs, because we like to keep the issue queue concise and actual.
If you think this issue is still relevant, please let us know. Especially if you’d like to help resolve the issue, either by helping us pinpointing the cause of a bug, or in implementing a fix or new feature.