#108028Database-Compare fails on database-names like "a.b.c"
Description
The database-compare tool fails if the database name contains more than one “.”
Steps to reproduce :
- create a running typo3-instance.
- rename the database to something like “a.b.c“
- call database compare-tool from BE or from install-tool
result : The compare-tool will fail with the message
"[ Doctrine\DBAL\Schema\Exception\TableAlreadyExists ] The table with name "a.b" already exists."
additional information :
In the database, the is neither a table “a”, nor “b”, nor “a.b”. The error-message is misleading.
In TYPO3 v12 this sort of database names didn’t create problems.
Reviews 4
- main 95194[WIP][!!!][TASK] Remove the array shaped schema migrator API
- 13.4 95480[BUGFIX] Allow database names containing a dot in schema migration
- 14.3 95479[BUGFIX] Allow database names containing a dot in schema migration
- main 94605[BUGFIX] Allow database names containing a dot in schema migration
Related issues 1
History 913
-
Garvin Hicking changed assigned to Stefan Bürk <span data-processor="relativetime" data-value="2025-11-19T13:49:04+00:00" > 11/19/25, 13:49 </span>
-
Oliver Hader changed target version <span data-processor="relativetime" data-value="2026-01-23T12:29:53+00:00" > 01/23/26, 12:29 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-03-31T09:05:28+00:00" > 03/31/26, 09:05 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-04-21T11:23:50+00:00" > 04/21/26, 11:23 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 94605 status
NewUnder Review <span data-processor="relativetime" data-value="2026-06-26T17:22:09+00:00" > 06/26/26, 17:22 </span> -
Gerrit Code Review pushed patch set 2 for main to change 94605 <span data-processor="relativetime" data-value="2026-08-02T17:15:34+00:00" > 08/02/26, 17:15 </span>
-
Benni Mack changed Sprint Focus On Location Sprint <span data-processor="relativetime" data-value="2026-08-06T16:02:40+00:00" > 08/06/26, 16:02 </span>
-
Stefan Bürk changed Related to #110420 <span data-processor="relativetime" data-value="2026-08-11T01:25:46+00:00" > 08/11/26, 01:25 </span>
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 95479 <span data-processor="relativetime" data-value="2026-08-31T07:27:47+00:00" > 08/31/26, 07:27 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 95480 <span data-processor="relativetime" data-value="2026-08-31T07:28:03+00:00" > 08/31/26, 07:28 </span>
-
Georg Ringer commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-08-31T07:55:13+00:00" > 08/31/26, 07:55 </span>Applied in changeset commit:37cb9d8c5b9cbbaf0d1de9dbc2c469852c7c4847.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-09-08T10:03:32+00:00" > 09/08/26, 10:03 </span>
I can confirm this issue in TYPO3 13.4.22. My database name was like “t3_13.4_sitename_stage”.
After “typo3 database:updateschema” command or running the database compare-tool, the TableAlreadyExists exception throws.
Renaming the database without “.” fixed this.