Bug #98518: Wrong version detection of database - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #98518

closed

Wrong version detection of database

Added by Stefan Froemken over 1 year ago. Updated over 1 year ago.

Status:

Closed

Priority:

Must have

Assignee:

Category:

Database API (Doctrine DBAL)

Target version:

12.1

Start date:

2022-10-04

Due date:

% Done:

100%

Estimated time:

TYPO3 Version:

PHP Version:

8.1

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

Hello,

I just try to install TYPO3 12.0, but install wizard fails because of:

MariaDB version too low
Your MariaDB version 5.5.5 is too old. TYPO3 CMS does not run with this version. Update to at least MariaDB 10.3.0

My .ddev/config.yaml:

mariadb_version: "10.3"

Server Version copied from PhpMyAdmin:

Server-Version: 10.3.32-MariaDB-1:10.3.32+maria~focal-log - mariadb.org binary distribution

I have started a xdebug session in TYPO3\CMS\Install\SystemEnvironment\DatabaseCheck\Platform\MySql.php. In method checkMySQLOrMariaDBVersion the Server string is:

MySQL 5.5.5-10.3.32-MariaDB-1:10.3.32+maria~focal-log

Seems the preg_match "/MySQL ((\d+\.)*(\d+\.)*\d+)/" has to be updated.

Stefan

Related issues 1 (1 open — 0 closed)

Actions

Copy link

Updated by Georg Ringer over 1 year ago

Status changed from New to Accepted
Priority changed from Should have to Must have

Actions

Copy link

Updated by Benni Mack over 1 year ago

Target version changed from 12.0 to 12.1

Actions

Copy link

Updated by Gerrit Code Review over 1 year ago

Status changed from Accepted to Under Review

Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/75991

Actions

Copy link

Updated by Stefan Bürk over 1 year ago

Stefan Frömken, can you test and verify if it works with the patch ? (composer patch etc) ?

Normaly having the 5.5.5- prefix in the version string means that a not-fully mariadb compat client version is used. Compat client libraries normall removes the fake prefix, which mariadb has to ship to avoid MySQL/MariaDB replication issues. At least from my research. Mainly it seems to occour on
windows servers.

However .. will check ddev the next days if I find a spare machine to install it. And eventually report it to ddev that thay may have to update the client library etc.

However, to be on the safe side I changed the regexp which should no properly deal with it.

Actions

Copy link

Updated by Gerrit Code Review over 1 year ago

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/75991

Actions

Copy link

Updated by Stefan Froemken over 1 year ago

Thank you Stefan,

I have tested your patch and it works.

I found the problem in MariaDB source code:
https://github.com/MariaDB/server/blob/826f9d4f7e99973cafe7654697d7c50b8b64b76b/include/mysql_com.h#L41

Further the PHP community was also not amused about it:
https://bugs.php.net/bug.php?id=78179
See answer of "[2019-07-21 17:43 UTC] requinix@php.net"
Quote: "...but the truth is that since 10.0 their versioning scheme is incompatible with MySQL's"

Actions

Copy link

Updated by Gerrit Code Review over 1 year ago

Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/75991

Actions

Copy link