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 2011/04/17 13:10:05 UTC
[jira] [Updated] (COUCHDB-1125) implement inclusive_start view
option
[ https://issues.apache.org/jira/browse/COUCHDB-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Lehnardt updated COUCHDB-1125:
----------------------------------
Attachment: inclusive_start.patch
Patch to implement inclusive_start.
Touches the btree, needs thorough review!
Doesn't break any tests so far.
Patch includes streamlining of internal query args handling.
> 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