couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raghuveer Kancherla <>
Subject what does batch=ok really mean
Date Fri, 30 Jul 2010 06:22:04 GMT

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.

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.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message