The Replica Schema Change process adds a new empty field when a field is renamed.
上次发布: July 27, 2017ArcSDE/Enterprise Geodatabase
漏洞 ID 编号
BUG-000089425
已提交
July 29, 2015
上次修改时间
January 28, 2021
适用范围
ArcSDE/Enterprise Geodatabase
找到的版本
10.2
状态
Will Not Be Addressed
开发团队已考虑过该问题或请求,并决定不会解决该问题。 问题的“其他信息”部分可能包含进一步说明。
附加信息
I actually don’t think it is a bug as our system is designed to work this way. Replication matches data by field name so if you change the field name, it won’t be able to match it. The behavior described with the schema changes is also expected and I think correct. We add fields that do not exist in the target with the schema differences tools by default but we do not delete fields by default – users need to choose to delete the field and thus make a conscience decision to do so. Don’ t see that as a data loss issue.