#91907tinytext columns cause schema inspector loop when adding an index on these columns
Description
Some columns (I didn’t check all, these are probably just some of them), like
sys_category.titlesys_file.namesys_file_metadata.title
define itself as
<columname> tinytext
or
@<columname> tinytext NOT NULL@</columname>
First minor problem: BLOB-type columns (like BLOB and TEXT and their differnet sizes) are not not-nullable (specifying NULL or NOT NULL on them has no effect at all).
When adding an index on these columns like
CREATE TABLE sys_category (
INDEX my_title_index (title(100))
);
The schema inspector will create the index first, but then always suggests to drop and recreate it, in an endless loop.
Why are these columns tinytext anyways? Instead of varchar(255)? tinytext is not Unicode-aware (it can only store 255 bytes, not 255 characters). Also it is a BLOB-type, which means usually it is way slower than varchar on lookup-time (depending on lots of factors, but it can never be faster than varchar, and usally it’s really slower).
I marked this as v9, but I assume it’s like this in any version.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 4
-
S P commented 07/31/20, 07:39
-
S P commented and changed TYPO3 Version
910 10/20/21, 06:09Valid on v10, still.
-
S P commented 10/16/24, 06:57
Works on v12 (these fields are still
tinytextinstead ofvarchar(255), but the schema inspector correctly detectd indexes on them).Ticket can be closed.
-
Oliver Bartsch commented and changed status
NewClosed 10/16/24, 07:12Closed as requested by author.
This seems only to happen with tinytext. Tested it on a text column (
sys_file.identifier) -> works perfectly.