Index on sys_file_processedfile is too large
Since #54234 a SQL error in the Upgrade Wizard / Database Compare is left open:
ALTER TABLE sys_file_processedfile ADD KEY identifier (storage,identifier);
Specified key was too long; max key length is 1000 bytes
"identifier" is varchar(512) but on utf8 charset every character needs 3 bytes of space. So the index is "too large" (for MyISAM).
Solution would be to limit the key to the first 332 chars.
[BUGFIX] Index on sys_file_processedfile is too large
Reviewed-by: Wouter Wolters
Tested-by: Wouter Wolters
Reviewed-by: Marcin Sągol
Tested-by: Marcin Sągol
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind
[BUGFIX] Index on sys_file_processedfile is still too large
On some systems even "332" characters is too large. To also cope with
potential utf8mb4 setups (1 char = 4 bytes), and staying under 1000 byte
limit, we reduce the amount of characters in the index to 249.