couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1125) implement inclusive_start view option
Date Sun, 17 Apr 2011 23:28:05 GMT

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

Randall Leeds commented on COUCHDB-1125:
----------------------------------------

Cool. What about inclusive=(start|end|both) instead and deprecating inclusive_end in the future?
Something pretty about it to me :)

> implement inclusive_start view option
> -------------------------------------
>
>                 Key: COUCHDB-1125
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1125
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: Jan Lehnardt
>            Priority: Minor
>         Attachments: inclusive_start.patch
>
>
> From COUCHDB-194:
> I suggest to generalize to left or/and right opened range. 
> Because, to select a left opened range of keys, we have to use a tip. 
> Exemple : 
> keys = [1, 2, 3, 4, 5] 
> to select where 2<key 
> We have to do : startkey=2&skip=1 
> But : 
> If keys are no unique, the "skip" tip no more works. 
> Ex: keys = [1, 2, 2, 3, 4, 5] 
> The request startkey=2&skip=1 doesn't work because a "2" key is returned. 
> (ps: non unique keys can be a wanted result)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message