Paul,
Yeah, the exclusiveness fits the general use pattern for using the
view. Ie, you process through the list remembering the sequence id of
the last doc you processed. When you restart you don't need to worry
that you've already processed the seq id you stored.
Paul
On Wed, May 20, 2009 at 4:39 AM, Paul Carey <paul.p.ca...@gmail.com> wrote:
> Hi
>
> I just noticed that startkey is exclusive when applied against
> _all_docs_by_seq but inclusive for all other queries. Is this
> intentional?
>
> Thanks
>
> Paul
>
> ====
>
> 09:25 : ~ $ curl -X PUT localhost:5984/sk_test
> {"ok":true}
> 09:28 : ~ $ curl -X PUT -d '{"_id":"1"}' localhost:5984/sk_test/1
> {"ok":true,"id":"1","rev":"1-1347026183"}
> 09:28 : ~ $ curl -X GET localhost:5984/sk_test
> {"db_name":"sk_test","doc_count":1,"doc_del_count":0,"update_seq":1,"purge_seq":0,"compact_running":false,"disk_size":14271,"instance_start_time":"1242808117550098"}
> 09:29 : ~ $ curl -X GET 'localhost:5984/sk_test/_all_docs_by_seq?startkey=0'
> {"total_rows":1,"offset":0,"rows":[
> {"id":"1","key":1,"value":{"rev":"1-1347026183"}}
> ]}
> 09:29 : ~ $ curl -X GET 'localhost:5984/sk_test/_all_docs_by_seq?startkey=1'
> {"total_rows":1,"rows":[]}
> 09:29 : ~ $ curl -X GET 'localhost:5984/sk_test/_all_docs?startkey="1"'
> {"total_rows":1,"offset":0,"rows":[
> {"id":"1","key":"1","value":{"rev":"1-1347026183"}}
> ]}
>
