Nobody mentioned it so far... with utf8mb4 which is 4-byte and can also store emoticons (we should never more use 3-byte utf8) and we can avoid errors like Incorrect string value: \xF0\x9F\x98\... we should not use typical VARCHAR(255) but rather VARCHAR(191) because in case utf8mb4 and VARCHAR(255) same part of data are stored off-page and you can not create index for column VARCHAR(255) but for VARCHAR(191) you can. It is because the maximum indexed column size is 767 bytes for ROW_FORMAT=COMPACT or ROW_FORMAT=REDUNDANT.

For newer row formats ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED (which requires newer file format innodb_file_format=Barracuda not older Antelope) maximum indexed column size is 3072. It is available since MySQL >= 5.6.3 when innodb_large_prefix=1 (disabled by default for MySQL <= 5.7.6 and enabled by default for MySQL >= 5.7.7). So in this case we can use VARCHAR(768) for utf8mb4 (or VARCHAR(1024) for old utf8) for indexed column. Option innodb_large_prefix is deprecated since 5.7.7 because its behavior is built-in MySQL 8 (in this version is option removed).

我知道现在已经很晚了，但是删除唯一键约束解决了这个问题。我没有使用TEXT或LONGTEXT列作为PK，但我试图使它独特。我得到了1170的错误，但当我删除了英国，错误也被删除了。

我不完全明白为什么。

为了索引，必须将列类型更改为varchar或整型。

另外，如果你想在这个字段中使用索引，你应该使用MyISAM存储引擎和FULLTEXT索引类型。

我曾经用过这个，也犯过你提到的错误:

CREATE INDEX idx_col1 ON my_table (col1);

然后我把它换成了这个，并解决了:

CREATE INDEX idx_col1 ON my_table (col1(255));

DROP该表并再次运行Spring Project。 这可能会有所帮助。 有时你重写了foreignKey。