Bug #104853: Analyze Database via Maintenance produces an error - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #104853

closed

Analyze Database via Maintenance produces an error

Added by Aristeidis Karavas about 1 month ago. Updated about 1 month ago.

Status:

Closed

Priority:

Should have

Assignee:

Stefan Bürk

Category:

Database API (Doctrine DBAL)

Target version:

Start date:

2024-09-07

Due date:

% Done:

Estimated time:

TYPO3 Version:

PHP Version:

8.3

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

TYPO3 v13
PHP 8.3
MySQL 10.6.18-MariaDB-0ubuntu0.22.04.1-log

I installed mask and created 2 new fields. Upon saving the element, i got a 500 error. Tried to add the fields via the Maintenance module, the same thing happened. This is the error

Typed property Doctrine\DBAL\Schema\TableDiff::$changedColumns must not be accessed before initialization

This is the line that produced the error

cms-core/Classes/Database/Platform/MariaDB1060Platform.php

public function getAlterTableSQL(TableDiff|DoctrineTableDiff $diff): array
{
    return $this->getCustomAlterTableSQLEngineOptions($this, $diff, parent::getAlterTableSQL($diff));
}

Ill try to add the stack trace as an image.

Not really sure why this happens

Files

Download all files

Screenshot 2024-09-07 at 20.44.28.png (137 KB) Screenshot 2024-09-07 at 20.44.28.png		Aristeidis Karavas, 2024-09-07 17:45
Screenshot 2024-09-07 at 20.47.56.png (121 KB) Screenshot 2024-09-07 at 20.47.56.png		Aristeidis Karavas, 2024-09-07 17:48
Screenshot 2024-09-07 at 20.49.18.png (171 KB) Screenshot 2024-09-07 at 20.49.18.png		Aristeidis Karavas, 2024-09-07 17:52

Related issues 2 (0 open — 2 closed)

Actions

Copy link

Updated by Aristeidis Karavas about 1 month ago

Category set to Database API (Doctrine DBAL)

Actions

Copy link

Updated by Garvin Hicking about 1 month ago

Status changed from New to Needs Feedback

Did you use T3v 13.2 as a release, or git main?

Which doctrine/dbal version is installed for you? You might need to pin to version 4.1 due to some issues.

Not 100% sure this is related, but maybe it helps. DB Analyzer has some quirks which are known and are to be addressed in v13, maybe not yet for 13.3 but definitely for 13.4 LTS

Actions

Copy link

Updated by Aristeidis Karavas about 1 month ago · Edited

i installed TYPO3 locally via composer

composer create-project "typo3/cms-base-distribution:^13" .

and then uploaded the composer.lock to my server and run composer install

which resulted to that on my composer.lock

"name": "typo3/cms-core",
"version": "v13.2.1",
"source": {
     "type": "git",
     "url": "https://github.com/TYPO3-CMS/core.git",
     "reference": "dd52f4568e6d9daeaf4bd83235d7eb9275785c11" 
},

As for dbal, this is from my composer.lock

"name": "doctrine/dbal",
"version": "4.1.1",
"source": {
    "type": "git",
     "url": "https://github.com/doctrine/dbal.git",
     "reference": "7a8252418689feb860ea8dfeab66d64a56a64df8" 
},

Actions

Copy link

Updated by Stefan Bürk about 1 month ago

Assignee set to Stefan Bürk

Duplicate of #104653.

The issue is, that Doctrine DBAL 4.1.* changed something (breaking) for the core,
which needed adoption within the core. That has been done on the very same day
of the Doctrine DBAL 4.1.0 release and contained within TYPO3 v13 main and will
be released with 13.3 then.

For 13.2.1 and earlier you need to either set Doctrine DBAL 4.1.0 and higher on conclict
or limit it in your project root composer.json. For an 13.3 update after it has been
released you need to remove it then (as 13.3 hard requires Doctrine DBAL 4.1 or newer).

See merged change [1] which raises doctrine and introduces the required changes on the
TYPO3 side.

[1] 85620: [TASK] Raise `doctrine/dbal:^4.1` | https://review.typo3.org/c/Packages/TYPO3.CMS/+/85620