Closed youngzil closed 3 weeks ago
I saw that there was a PR #4725 that made some optimizations for the field length unification, but it did not include the three tables commit
, namespace
, and release
. Why is this?
It includes the commit
, namespace
, and release
tables but appears to miss the NamespaceName
and ClusterName
fields.
It includes the
commit
,namespace
, andrelease
tables but appears to miss theNamespaceName
andClusterName
fields.
I think this can be fixed and is safe.
你的特性请求和某个问题有关吗?请描述
在实际使用时,发现日志经常会有少量的数据库字段超长的报错,发现是
Release
表的NamespaceName
字段是 varchar(500),但是InstanceConfig
表的ConfigNamespaceName
字段是 varchar(32)AppNamespace
表中Name
字段是varchar(32)Cluster
表中Name
字段是 varchar(32),Commit
表中ClusterName
字段是 varchar(500)相同含义的字段在所有表中是否有必要同一,避免一些潜在的问题
清晰简洁地描述一下你希望的解决方案
清晰简洁地描述一下这个特性的备选方案
其它背景
在这里添加和这个特性请求有关的背景说明、截图