[ 
https://issues.apache.org/jira/browse/COUCHDB-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744262#action_12744262
 ] 

Chris Anderson commented on COUCHDB-446:
----------------------------------------

crucial to my last comment yet untyped:

It'd be nice to make lists work on built in views like _all_docs and _changes.

not for this patch, but just as long as we are on the topic of unified APIs...

I think this patch is ready to go in.

> allow list function and view function to be in different design docs.
> ---------------------------------------------------------------------
>
>                 Key: COUCHDB-446
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-446
>             Project: CouchDB
>          Issue Type: New Feature
>          Components: Database Core
>            Reporter: Mark Hammond
>             Fix For: 0.10
>
>         Attachments: x_doc_list.patch, x_doc_list_jan.patch
>
>
> There has been some discussion on #couchdb how it might be desirable to use a 
> list function where the list and the view are in separate documents.  Among 
> the use-cases is so a list and view can use different languages.
> I'm attaching a patch which extends the URL syntax for list views - before my 
> patch, the last portion of the path must be a view name.  My patch allows for 
> the existing behaviour, or for the tail to be 2 elements - another design 
> document name *and* the view name.  Includes a test.

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

Reply via email to