Mailing-List: contact couchdb-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-dev@incubator.apache.org
Message-ID: <1662603335.1211758195686.JavaMail.jira@brutus>
Date: Sun, 25 May 2008 16:29:55 -0700 (PDT)
From: "Christopher Lenz (JIRA)" <jira@apache.org>
To: couchdb-dev@incubator.apache.org
Subject: [jira] Updated: (COUCHDB-21) _design_docs view
In-Reply-To: <424859698.1205020786478.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christopher Lenz updated COUCHDB-21:
------------------------------------

    Issue Type: Wish  (was: Bug)

> _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: Minor
>
> 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.