-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
文章内容很长时无法保存 #2832
Comments
/assign @JohnNiang |
在 MySQL 中, Workaround(临时解决方案)尝试修改 extension 表的 data 字段类型为:MEDIUMBLOB 或者 LONGBLOB。 alter table extensions modify data mediumblob; 参考: |
已将 |
我觉得比较理想的机制是这样的,不知是否正确: 用户保存/发布文章时,如果长度达到 (可选)弄一个定时任务检查数据库中文章,如果长度都小于某个类型的 max size ,则将 data 的类型降级。 |
其实不用降级的。Blob、MediumBlob 和 LongBlob 本身就是 |
… at row 1" (#2833) #### What type of PR is this? /kind improvement /area core /milestone 2.0.1 #### What this PR does / why we need it: See #2832 and #2832 (comment) for more. For a workaround, please refer to: - #2832 (comment) But, there are still limitations here: - For MySQL: ~4GB - For PosgreSQL: ~1GB #### Which issue(s) this PR fixes: Fixes #2832 #### Does this PR introduce a user-facing change? ```release-note 修复因文章过长导致无法保存数据的问题 ```
是什么版本出现了此问题?
2.0.0
使用的什么数据库?
MySQL 5.7
使用的哪种方式部署?
Docker Compose
在线站点地址
https://blog.ataw.top
发生了什么?
有一篇 很长的文章,估计有几千字吧。编辑之后无法保存,也无法发布。
相关日志输出
附加信息
前端 console:
从 Halo 1.5 还是 1.6 迁移过来的,导入数据时没出问题,但是想更新文章就不行了。
The text was updated successfully, but these errors were encountered: