如何从设计角度来对待CouchDB修订版？ [英] How should CouchDB revisions be treated from a design perspective?

问题描述

我可以看出，CouchDB修订版不会被视为文本版本控制中的修订版本。从其他职位看，他们似乎被视为存在直到粗调紧凑操作被调用的临时数据。

Near as I can tell, CouchDB revisions are not to be treated like revisions in the document versioning sense of the word. From glancing at other posts, they seem to be regarded as transient data that exists until a coarse-grained compact operation is called.

我的问题是，如果我有兴趣使用CouchDB来维护文档，以及这些文档的版本历史记录，那么我应该允许它由CouchDB修订本身来处理，还是应该在顶层构建一个能够在紧凑型操作？

My question is, if I am interested in using CouchDB to maintain documents, as well as a version-history of those documents, should I allow that to be handled natively by CouchDB revisions, or should I build a layer on-top that will survive a compact operation?

我以为后者只是因为Couch不会复制文档的修订版本，只是最新的更新。这使我认为修订是一个错误的名称，因为它更多的是稳定复制的数据结构。

I am thinking the latter, simply because Couch does not replicate revisions of documents, only the latest update. This makes me think revision is a mis-leading name, as it's more of a data structure for stabilizing replication.

推荐答案

您必须构建该层，因为couchdb修订版不是您的数据版本控制系统。

You must build that layer because couchdb revisions are not a versioning system for your data.

'修订版'是误导性的，所以版本也是如此，迄今为止所建议的每个名称也是如此。建议欢迎，如果只是确认这是多么棘手的命名。

'revision' is misleading, and so is 'version' and so is every name that has been suggested so far. Suggestions welcome, if only to confirm how tricky naming this is.

这篇关于如何从设计角度来对待CouchDB修订版？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！