couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nolan Lawson (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-2227) Feature request: _all_docs?exclude_ddocs=true
Date Mon, 21 Apr 2014 23:06:15 GMT


Nolan Lawson commented on COUCHDB-2227:

For a generic exclude operation, how about something like {{exclude_range=\[startkey, endkey]}}?
It would work for all three of \_changes, \_view, and \_all\_docs.  Then our {{include_ddocs=false}}
would just become {{exclude_range=\["design_", "design/"]}}, which is still kinda gnarly,
but at least it doesn't require two separate requests.  And it might have uses beyond excluding

> Feature request: _all_docs?exclude_ddocs=true
> ---------------------------------------------
>                 Key: COUCHDB-2227
>                 URL:
>             Project: CouchDB
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: HTTP Interface
>            Reporter: Nolan Lawson
>            Priority: Minor
> Design docs are included in {{\_all_docs}} results, which is by design (hyuk hyuk). 
However, this can be surprising and unwanted behavior for new users, and plus, sometimes it's
tricky to exclude them, e.g. if your docids come both before and after the {{_}} character:
> {code:javascript}
> {"total_rows":6,"offset":0,"rows":[
> {"id":"Bar","key":"Bar","value":{"rev":"1-967a00dff5e02add41819138abb3284d"}},
> {"id":"Foo","key":"Foo","value":{"rev":"1-967a00dff5e02add41819138abb3284d"}},
> {"id":"_design/temp","key":"_design/temp","value":{"rev":"1-ee20bd300ce7ffa18e9ef1144fa50fd4"}},
> {"id":"_design/temp2","key":"_design/temp2","value":{"rev":"1-9b626494fef9a884a383345540c29e97"}},
> {"id":"bar","key":"bar","value":{"rev":"1-967a00dff5e02add41819138abb3284d"}},
> {"id":"foo","key":"foo","value":{"rev":"1-967a00dff5e02add41819138abb3284d"}}
> ]}
> {code}
> What I would like is a query param like {{exclude_ddocs}}, which defaults to false and
would only return non-design documents, but otherwise function exactly the same.  What {{offset}}
and {{total_rows}} would do in this case is up to you.
> Workaround: The best workaround is to do two separate queries, one with the parameters
{{endkey=%22_design/%22}} and the other with {{startkey=%22_design0%22}}. But this is not
particularly elegant.

This message was sent by Atlassian JIRA

View raw message