[COUCHDB-937] inclusive_end does not work as expected

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.0.1

Environment

x86 64bit Arch Linux 2.6.35

• Assignee: Unassigned
• Reporter: Robert Newson
• Created: 06/Nov/10 16:17
• Updated: 11/May/11 16:05
• Resolved: 11/May/11 16:05

Description

On behalf of Marco Monteiro;

I expected both of the following queries to return the result of the first one.
The difference betwen the two queries is the inclusive_end argument.

ruby-1.9.2-p0 > db.view("calculate/work_duration_by_project_id_and_start_time", :group_level=>2, :startkey => ["0da7979149f2d71f1f5c2361c400c8f2", "2000"], :endkey => ["0da7979149f2d71f1f5c2361c400c8f2", "2011"], :inclusive_end=>true)["rows"].each do |r| puts r end; nil

{"key"=>["0da7979149f2d71f1f5c2361c400c8f2", "2000-03-01 00:00:00"], "value"=>12340} {"key"=>["0da7979149f2d71f1f5c2361c400c8f2", "2010-10-19 23:00:00"], "value"=>8400} {"key"=>["0da7979149f2d71f1f5c2361c400c8f2", "2010-10-24 23:00:00"], "value"=>12900} {"key"=>["0da7979149f2d71f1f5c2361c400c8f2", "2010-10-28 23:00:00"], "value"=>70975}

=> nil

ruby-1.9.2-p0 > db.view("calculate/work_duration_by_project_id_and_start_time", :group_level=>2, :startkey => ["0da7979149f2d71f1f5c2361c400c8f2", "2000"], :endkey => ["0da7979149f2d71f1f5c2361c400c8f2", "2011"], :inclusive_end=>false)["rows"].each do |r| puts r end; nil

{"key"=>["0da7979149f2d71f1f5c2361c400c8f2", "2000-03-01 00:00:00"], "value"=>12340} {"key"=>["0da7979149f2d71f1f5c2361c400c8f2", "2010-10-19 23:00:00"], "value"=>8400} {"key"=>["0da7979149f2d71f1f5c2361c400c8f2", "2010-10-24 23:00:00"], "value"=>12900} {"key"=>["0da7979149f2d71f1f5c2361c400c8f2", "2010-10-28 23:00:00"], "value"=>70975} {"key"=>["0da7979149f2d71f1f5c2361c40c11d5", "2010-10-28 23:00:00"], "value"=>7275} {"key"=>["0da7979149f2d71f1f5c2361c40c6920", "2010-10-28 23:00:00"], "value"=>16975} {"key"=>["0da7979149f2d71f1f5c2361c40c73ee", "2010-10-28 23:00:00"], "value"=>24100} {"key"=>["0da7979149f2d71f1f5c2361c40c7ddb", "2010-10-28 23:00:00"], "value"=>7275} {"key"=>["5465fdb28f9aae885dba76e4860010d4", "2000-03-01 00:00:00"], "value"=>600} {"key"=>["5465fdb28f9aae885dba76e4860010d4", "2010-10-27 23:00:00"], "value"=>7200} {"key"=>["5465fdb28f9aae885dba76e486001d07", "2000-03-01 00:00:00"], "value"=>1420} {"key"=>["5465fdb28f9aae885dba76e4860020b4", "2000-03-01 00:00:00"], "value"=>1420} {"key"=>["5465fdb28f9aae885dba76e4860021c8", "2000-03-01 00:00:00"], "value"=>600}

=> nil

All other agruments being equal, I expect a query with inclusive_end set to true to never return less rows than one with inclusive_end set to false.
Am I missing something?

I have checked the request made by the CouchRest library (this could be a CouchRest bug), and the request url is as expected.

Issue Links

• is duplicated by: COUCHDB-1047 endkey ignored when inclusive_end=false for reduce view calls