We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
服务-添加api文档时:提示Error 1406 (22001): Data too long for column 'content' at row 1,这里内容限制能设置更大吗?可能一个服务的api接口过多时,添加就会有问题。
No response
APINTO Dashboard version: Version v1.4.1-beta-2025-01-14T10:32:10Z
Operating system (run uname -a):
uname -a
The text was updated successfully, but these errors were encountered:
好的,收到您的反馈,后续发布的新版本我们将把该字段的mysql类型改为longtext 您也可以自行先在mysql中修改该字段类型 数据库表名:api_doc 字段名:content
api_doc
content
Sorry, something went wrong.
好的,收到您的反馈,后续发布的新版本我们将把该字段的mysql类型改为longtext您也可以自行先在mysql中修改该字段类型 数据库表名: 字段名:api_doc``content
api_doc``content
谢谢回复,自己测试过改数据库字段,服务重启会自动覆盖修改的字段类型,自己改了api_doc字段类型,服务发布的时候还是报这个问题,应该还有server_doc、service_commit 表中有字段超长了
No branches or pull requests
Current Behavior
服务-添加api文档时:提示Error 1406 (22001): Data too long for column 'content' at row 1,这里内容限制能设置更大吗?可能一个服务的api接口过多时,添加就会有问题。
Expected Behavior
No response
Error Logs
Steps to Reproduce
No response
Environment
APINTO Dashboard version: Version v1.4.1-beta-2025-01-14T10:32:10Z
Operating system (run
uname -a
):The text was updated successfully, but these errors were encountered: