Field Content Case Sensitivity

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 字段内容大小写

| username: 等一分钟

May I ask, for an already created TiDB cluster, if you want the content of varchar type fields to be case-insensitive, do you have to rebuild the cluster?

2
| username: xfworld | Original post link

Currently, it can only be rebuilt…

3
| username: 等一分钟 | Original post link

Regardless of which version, right?

4
| username: xfworld | Original post link

You can refer to this document to try it out:

However, the following characteristics determine that the cluster cannot support more methods:

image
image807×228 11.4 KB

It is recommended to consider carefully when planning the character set and collation of the cluster…

5
| username: wuxiangdong | Original post link

Modify the sorted set:
alter table xxx COLLATE=

6
| username: wuxiangdong | Original post link

Modify the field

alter table test1 modify column name varchar(20) COLLATE utf8mb4_bin DEFAULT NULL
7
| username: wuxiangdong | Original post link

Keep the sorted set consistent, otherwise, associated queries can easily encounter issues…

8
| username: 等一分钟 | Original post link

Changing the character set doesn’t work.

9
| username: xiaohetao | Original post link

The image you provided is not accessible. Please provide the text you need translated.

10
| username: xiaohetao | Original post link

The image you provided is not accessible. Please provide the text content you need translated.

11
| username: alfred | Original post link

In this situation, you can only rebuild and then migrate.

12
| username: xiaohetao | Original post link

Yes.