Question

www.un.org/Depts/DGACM/index_spanish.htm 在使用更新的手稿时,怎么会发生冲突? 在撰写一项强有力的更新职能时,我是否应该对冲突处理法感到关切?

如Document Update Handlers所述,CouchDB 0.10,后允许对需要服务器-侧文件进行修改。

更新处理人员可以处理非初专干事格式;但其他主要特征是:

An HTTP front-end to arbitrarily complex document modification code
Similar code needn t be written for all possible clients—a DRY architecture
Execution is faster and less likely to hit a revision conflict

我不清楚第三点。在当地执行,更新的手稿将更快地运作,相对较少。但是,在争辩激烈的情况下,这并不能保证得到成功的更新。 Or 更新的手稿是否保证了成功更新?

Answer 1

www.un.org/Depts/DGACM/index_spanish.htm 在使用最新处理器时仍有可能发生最新冲突。

Due to the reduced "round-trip time," the chance of an update conflict is lower but not zero. A conflict will feel normal: a 409 response code with this JSON:

{"error":"conflict","reason":"Document update conflict."}

I successfully triggered a conflict using the document update handler example, and running curl twice in short succession in the shell.

curl -v -X PUT 
http://localhost:5984/db/_design/app/_update/accumulate/my_doc?amount=10 
& curl -X PUT 
  http://localhost:5984/db/_design/app/_update/accumulate/my_doc?amount=1

治疗性反应(大多)是201个,另一个是409个。

Document update handlers do not fundamentally change CouchDB

Updates are subject to conflicts, as well as validation failures (401 Unauthorized, 403 Forbidden, etc.)

Document update handlers do not fundamentally change CouchDB

友情链接