#95577Database compare fails on index creation when disabling file metadata translation
Description
ext:core/ext_tables.sql has this for table sys_file_metadata :
KEY fal_filelist (l10n_parent,sys_language_uid)
However, following Feature #90114 (https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/10.3/Feature-90114-MakeTranslationOfFilelistOptional.html) removes sys_file_metadata.l10n_parent – making the Database Compare fail when it tries to create this hardcoded index, because the column does not exist.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 2
History 8
-
Oliver Hader commented and changed status
NewAccepted <span data-processor="relativetime" data-value="2021-10-21T13:58:24+00:00" > 10/21/21, 13:58 </span> -
Stefan Bürk changed Related to #104316 <span data-processor="relativetime" data-value="2024-08-05T21:23:52+00:00" > 08/05/24, 21:23 </span>
-
S P commented and changed TYPO3 Version
1012 <span data-processor="relativetime" data-value="2024-12-18T10:34:51+00:00" > 12/18/24, 10:34 </span>Still valid in v12
-
S P commented and changed TYPO3 Version
1213 <span data-processor="relativetime" data-value="2024-12-19T09:27:12+00:00" > 12/19/24, 09:27 </span>In TYPO3 13 the error message is different, but is caused by the same valid configuration. The Schema Updater still fails to correctly set the fields and/or indexes.
Syntax error or access violation: 1071 Specified key was too long; max key length is 3072 bytes
In v13
sys_file_metadata.l10n_parentis not removed but converted to LONGTEXT if$GLOBALS['TCA']['sys_file_metadata']['ctrl']['languageField'] = null;
which is allowed per #90137 .
This is too big for the index
KEY fal_filelist (l10n_parent,sys_language_uid) -
Stefan Bürk changed Related to #96729 <span data-processor="relativetime" data-value="2026-04-14T21:24:22+00:00" > 04/14/26, 21:24 </span>
-
Stefan Bürk commented <span data-processor="relativetime" data-value="2026-04-14T21:26:57+00:00" > 04/14/26, 21:26 </span>
In v14 the specific field handles the index now along the way,
which has been added with `#96729`.However, I’ll keep that open for now because this is literally
more a generic issue and I would guess related or similar tohttps://forge.typo3.org/issues/105438
just not that obvious. 105438 fails already reading `ext_tables.sql`
and never reaches the database compare logic or the DefaultTcaSchema
stuff at all. -
S P commented <span data-processor="relativetime" data-value="2026-06-11T07:57:41+00:00" > 06/11/26, 07:57 </span>
This works on v14, because the index and field are now fully autogenereted by the DB compare tool without any hardcoded stuff. Unsetting the TCA config also removes index and field.
I consider this specific issue as solved.
-
Garvin Hicking commented and changed status
AcceptedClosed <span data-processor="relativetime" data-value="2026-06-11T14:25:14+00:00" > 06/11/26, 14:25 </span>Thank you, I pinged stefan and we agree to close :)
More generic: Database analyzer should check whether fields used in indexes do actually exist for a particular table.