Google云端硬盘SDK docid已更改-如何将旧docid存储的文档与新文档相关联? [英] Google Drive SDK docid changed - How to relate documents stored by old docid to the new one?

问题描述

似乎Google应用程序域中所有Google云端硬盘文档的docid都已更改...

It appear that the docid's changed for all google drive documents on our google apps domain...

• 会再次更改吗?
• 为什么更改了?(我在这个主题上的google/yahoo/bing搜索没有任何用处-没有其他人会遇到这种情况吗?对我来说，这似乎发生在1月16日左右/17th)

• Will it change again?
• Why was it changed? (my google/yahoo/bing searches on this subject turn up nothing useful - is no one else experiencing this? For me it seems to have happened at around Jan 16/17th)

最重要的是:

• 是否可以将所有旧docid交叉引用到相应的新docid?

推荐答案

找到了更多信息.根本原因是从旧的演示文稿编辑器迁移到新的演示文稿编辑器.新的编辑器一直是默认设置，但是要完全切换所有旧的演示文稿，需要进行转换.由于各种技术原因，如果不为每个演示文稿创建新的文件条目，则无法执行此操作.这发生在大约6个月前，当时对文档进行了同样的操作.

Found out some more info. The root cause is a migration from the old presentation editor to the new one. The new editor has been the default for a while, but to complete switch over all the older presentations needed to be converted. For various technical reasons, it wasn't possible to do this without creating new file entries for each presentation. This happened once before about 6 months ago when the same thing was done for documents.

可以通过检查更改提要来重新映射ID.删除和create将显示为单独的事件，但是如果您要先进行删除，然后再创建具有相同标题的文件，则可以建立文件ID的映射.不是完全万无一失，而是一次性操作.

It is possible remap the IDs by checking the change feed. The delete & create will appear as separate events, but if you look for deletes followed by a create of a file with the same title you can build up a mapping of the file IDs. Not entirely foolproof, but its a one time operation.

因此，事实证明ID并没有像原来那样具有不变性...

So turns out IDs aren't quite as immutable as made out to be...

这篇关于Google云端硬盘SDK docid已更改-如何将旧docid存储的文档与新文档相关联?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！