Scott, It was dropped in a big refactor that Damien did. I'm working on adding it back in, but the specifics of how it will operate are yet to be determined. (For instance, a view won't be available using update=false until it has been completely calculated at least once. We're also thinking about update=status for a rough window into view generation progress.)
update=false should be back before 1.0, and hopefully in the next few weeks. Chris On Thu, Nov 6, 2008 at 5:13 PM, Scott Raio <[EMAIL PROTECTED]> wrote: > Any ideas to why update=false is broken? > > https://issues.apache.org/jira/browse/COUCHDB-77 > -- Chris Anderson http://jchris.mfdz.com
