yes, stale=ok won't help if you've never built the view. but if you
hit your view without stale=ok every N minutes from a cron job or
something, then you can always use stale=ok from your "real" clients,
and they'll never block for a view update. You'll always be five
minutes behind, but I think th
Yeah, but for new queries it would return empty set until all documents are
processed, right?
This makes debugging new queries a bit tricky.
You have to pick unbiased 2-3K documents into separate database, test your
queries there while they're fast to build and then use them on big database.
On M
You can also pass stale=ok if you don't need the latest results from a view.
http://wiki.apache.org/couchdb/HTTP_view_API
B.
On Mon, Jun 22, 2009 at 3:46 PM, Sergey Shepelev wrote:
> From my poor experience with couch, i think that your task (ever expanding
> set of data, no updates) is perfect
>From my poor experience with couch, i think that your task (ever expanding
set of data, no updates) is perfect for couch.
But, you should
also consider that expanding-only set of data is a good task for
constant databases too. Though, you would run into a expansive process
writing a nice querying
Hi All,
I am new to non-rdbms storage systems. I am working on an application in
which we need to log different user actions as plain text. I am not of the
opinion to make use of our rdbms for this activity as writing this on a
rdbms can be an expansive process.
Can I make use of Couch DB f
