incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From J Chris Anderson <jch...@gmail.com>
Subject Re: what does batch=ok really mean
Date Fri, 30 Jul 2010 19:51:05 GMT

On Jul 29, 2010, at 11:22 PM, Raghuveer Kancherla wrote:

> Hi,
> 
> In batch=ok mode, from the dicussion on the wiki / couchdb book it seems
> like the document is written into the memory and then flushed to disk at a
> later time. I dont really care about the possible data losses in this short
> period of time if the server crashes etc.

batch=ok returns 202 Accepted, so it could be some time before the document is accessible
for reads. Also, it doesn't check for rev mismatch, so better to not use batch=ok if you care
about what you are writing.

> 
> What is not clear to me is, what happens if another thread in my application
> tries to access this document before it is flushed to disk. In my case I
> need this document to be available immediately from the output of a view
> that I will access immediately after this document is added.
> 
> Thanks,
> Raghu
> http://raghuveer.info


Mime
View raw message