#110761Let the Database Analyzer ignore configured tables on the Default connection
Description
Problem
The analyzer introspects every table of the Default database. One column of a type Doctrine does not know aborts the whole analysis:
Doctrine\DBAL\Exception\InvalidArgumentException Unknown database type "vector" requested, TYPO3\CMS\Core\Database\Platform\MariaDB110700Platform may not support it.
The concrete case is MariaDB VECTOR (#106585), but any unmapped type does this, even for a table that is not declared in any ext_tables.sql. Today the only way out is a separate database, because the analyzer cannot be told to leave a table alone.
This is not a request for VECTOR support. It is a request for a way to mark tables as not managed by TYPO3.
Proposal
ConnectionMigrator::buildSchemaDiff() already sets a Doctrine SchemaAssetsFilter for non-default connections. Extend this to the Default connection with a configurable exclusion list:
- New key, e.g.
TYPO3_CONF_VARS['DB']['Connections']['Default']['unmanagedTables'](list of table names), empty by default. - Apply it as
SchemaAssetsFilterinbuildSchemaDiff(); combine with the existing mapping filter on other connections. - Remove the names from
$toSchemaas well, so a strayext_tables.sqldeclaration produces no CREATE. The method does this for views already; same pattern. - Open question: additionally a PSR-14 event so an extension can declare its own tables in code.
- Functional test, Feature changelog.
Measured (TYPO3 14.3.7, DBAL 4.4.4, MariaDB 11.8.8)
Doctrine checks the filter before it converts a table’s columns (AbstractSchemaManager::listTables()), so the unknown type is never touched.
Table in the TYPO3 database:
CREATE TABLE tx_zzprobe_vector (
uid int unsigned NOT NULL AUTO_INCREMENT,
v VECTOR(4) NOT NULL,
PRIMARY KEY (uid),
VECTOR INDEX (v)
);
| Setup | getUpdateSuggestions() for Default |
|---|---|
| unchanged core | Unknown database type "vector" |
setSchemaAssetsFilter() excluding the table |
no exception, no suggestions |
for comparison: vector mapped to BINARY via driver middleware |
no exception, but proposes RENAME TO zzz_deleted_tx_zzprobe_vector |
Out of scope
VECTOR in ext_tables.sql (#106585), custom Doctrine types (#93637), creating the excluded table (its owner does that).
Effort
Roughly 30 to 50 lines plus one functional test and a changelog entry.
Related: #106585, #93637
Disclaimer: this proposal was drafted with the help of an AI assistant (Claude). The code analysis and the measurements were verified by hand on a local DDEV TYPO3 14.3.7 installation.
Reviews 1
Related issues 4
History 36
-
Julian Mair changed Related to #106585 Related to #93637 <span data-processor="relativetime" data-value="2026-09-22T09:45:34+00:00" > 09/22/26, 09:45 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 95987 status
NewUnder Review <span data-processor="relativetime" data-value="2026-09-23T06:16:41+00:00" > 09/23/26, 06:16 </span> -
Gerrit Code Review pushed patch set 2 for main to change 95987 <span data-processor="relativetime" data-value="2026-09-23T07:03:29+00:00" > 09/23/26, 07:03 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 95987 <span data-processor="relativetime" data-value="2026-09-24T11:19:08+00:00" > 09/24/26, 11:19 </span>
-
Georg Ringer changed Related to #103154 <span data-processor="relativetime" data-value="2026-10-17T05:51:05+00:00" > 10/17/26, 05:51 </span>
-
Georg Ringer changed Related to #110420 <span data-processor="relativetime" data-value="2026-10-17T05:52:41+00:00" > 10/17/26, 05:52 </span>