couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <>
Subject [jira] [Resolved] (COUCHDB-1211) startkey_docid alone does start with that document id
Date Sun, 03 Jul 2011 14:39:21 GMT


Robert Newson resolved COUCHDB-1211.

    Resolution: Fixed

Updated wiki page with clarification that these two _docid parameters are only for paginating
when startkey/endkey have duplicates.

It is not practical to support starting-by-docid as the view index does not contain an index
on that value (the index is [key, doc_id]).

> startkey_docid alone does start with that document id
> -----------------------------------------------------
>                 Key: COUCHDB-1211
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>    Affects Versions: 1.1
>         Environment: Windows 7
>            Reporter: Jan Schulz
>            Priority: Minor
> I tried to iterator over a view in steps and tried to use the doc._id as a starting point
for the next step:
> http://localhost:5984/test3/_design/testdesign/_view/testview?skip=1&startkey_docid=<lastID>&limit=10
> with <lastID> as the last already seen ID. The result was that this value wasn't
used at all in the results: it always returned the 2-11 (doe to skip)  values and I got a
infinitive loop. From the documentation in the wiki I would have expected that the startkey_docid
is enought to specify the first entry of the resultset.
> It would be nice if you could either clarify the documentation (
 or implement the starting-by-docid feature.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message