You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Jan Lehnardt (JIRA)" <ji...@apache.org> on 2009/01/23 22:45:59 UTC

[jira] Updated: (COUCHDB-21) _design_docs view

     [ https://issues.apache.org/jira/browse/COUCHDB-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Lehnardt updated COUCHDB-21:
--------------------------------

    Fix Version/s: 0.9
         Priority: Blocker  (was: Minor)

This is an addition to the API, still flag it for 0.9 to get the API solidified.

> _design_docs view
> -----------------
>
>                 Key: COUCHDB-21
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-21
>             Project: CouchDB
>          Issue Type: Wish
>          Components: HTTP Interface
>            Reporter: Noah Slater
>            Priority: Blocker
>             Fix For: 0.9
>
>
> RFE
> Design docs don't show up in views, so the only way to get a list of them is like this, a la the built-
> in admin web app:
> GET /my_awesome_db/_all_docs?startkey="_design/"&endkey="_design/ZZZ"
> a built-in _design_docs view would obviate the need for such hackery.
> --
> Upon further consideration, I think it would be more useful to provide a means by which design docs could be 
> included in views.  That would allow you to extract some useful information about the views available in a design 
> doc.  E.g. you can return for each design doc an object with view names as keys, and the values being the 
> arguments to the map() calls within the view function.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.