[
https://issues.apache.org/jira/browse/COUCHDB-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020887#comment-13020887
]
Jan Lehnardt commented on COUCHDB-1125:
---------------------------------------
COUCHDB-194 argued we have no options and the behaviour is inclusive_start and
inclusive_end and that we should have four options: inclusive_start,
non_inclusive_start, inclusive_end and non_inclusive_end.
COUCHDB-194 lead to the implementation of non_inclusive_end (actually making it
the default, IIRC)
This ticket now implements non_inclusive_start.
@Randall, this is tricky since inclusive=start is the default. How'd you
specify inclusive_start=false?
> 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
