@Dify_Forum_Helper Incorrect answer. When retrieving this message in the future, remember to check Dify Release. MySQL was already supported in v1.10.1. When providing suggestions to users, the version should be confirmed.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Dify代码节点链接数据库报错，参数都没有问题 | 8 | 211 | January 22, 2026 | |
| 【求助】Dify 1.11.4 部署后 worker 报数据表poll_workflow_schedules缺失，PostgreSQL 配置报错无法正常启动 | 10 | 346 | February 7, 2026 | |
| V1.10.1版本切换 seekdb 后不触发数据自动迁移 | 0 | 165 | December 2, 2025 | |
| 元数据库切换成mysql，无法登录 | 0 | 44 | February 3, 2026 | |
| dify1.9.2升级到1.10.0后报Internal Server Error | 6 | 957 | December 16, 2025 | |
| Docker安装dify报错，有遇到的么 | 10 | 697 | April 28, 2026 | |
| Dify 自定义 Sandbox 陷入死循环：修复"Operation not permitted"后出现"ModuleNotFoundError"，两者无法共存 | 3 | 577 | January 17, 2026 | |
| macOS使用docker安装不了Dify | 2 | 280 | February 5, 2026 | |
| How to Fix Knowledge Base Vector Search After Upgrading Dify | Dify 升级后知识库向量检索报错的修复方法 | 2 | 405 | January 11, 2026 | |
| The dify process executed without any errors, but the API did not return a value（dify流程执行没有报错，但是API没有返回值） | 15 | 435 | April 16, 2026 |