[Question] 脱敏字段无法新增

[flapjackegg]

描述问题
在数据源里添加脱敏字段(已有 17 个)，保存后提示保存成功，但再次进入页面后发现没有保存，容器没有错误日志，有一条 Update 日志，数据库里面查询也没有保存上，不知道是有其他设置，还是有数量要求？

复现
重现该行为的步骤:

1. 在数据源里，点击详情，添加脱敏字段，此时还能看到字段在列表里
2. 保存，提示数据源信息已更新，无报错
3. 再次刷新页面，进入数据源详情，发现字段没有被保存
4. docker logs -f yearning，有 update 更新日志，无报错日志
5. 进入数据库查询数据，发现没有保存

期望的结果
期望脱敏字段能被顺利保存

截图
敏感数据，不便截图

部署方式

• [*] Docker
• Manual

环境 (请填写环境信息):

• 操作系统: Ubuntu 24.04.1
• 浏览器 Chrome
• 版本号 Chrome 139.0.x yearning 3.1.9

额外的日志信息
无其他日志

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Title: [Question] Desensitization field cannot be added

Description of the problem
Add a desensitization field to the data source (there are 17 already). After saving, it is prompted to save it successfully. However, after entering the page again, it is found that it is not saved. The container has no error logs. There is an Update log. The query in the database is not saved. I wonder if there are other settings or quantity requirements?

Reappearance
Steps to reproduce the behavior:

1. In the data source, click Details to add the desensitization field. You can also see the fields in the list.
2. Save, prompting that the data source information has been updated, no errors have been reported
3. Refresh the page again, enter the data source details, and find that the field is not saved
4. docker logs -f yearning, update update log, no error log
5. Enter the database to query the data and find that it is not saved

** Expected results**
I hope that the desensitization field can be saved smoothly

screenshot
Sensitive data, inconvenient screenshots

Deployment method

• [*] Docker
• Manual

Environment (Please fill in the environment information):

• Operating System: Ubuntu 24.04.1
• Browser Chrome
• Version number Chrome 139.0.x yearning 3.1.9

Extra log information
No other logs

[flapjackegg]

找到问题原因了，insulate_word_list 这个字段是 VARCHAR(200)，刚好用满了，修了一下表结构就好了

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

The reason for the problem was found. The field insulate_word_list is VARCHAR(200), and it just happens to be fully used. Just fix the table structure.