couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-388) throw an error if the view query range can contain no rows
Date Thu, 18 Jun 2009 21:24:07 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721501#action_12721501
] 

Paul Joseph Davis commented on COUCHDB-388:
-------------------------------------------

Just went to implement this and realized we'd be throwing an error when there are no rows
returned by the view. Which is obviously great for letting beginners figure out reverse=true
semantics, but it would throw an error just because a view doesn't return any results.

In other words, do we want to force people to do something like ?empty=ok in their views that
might have zero rows returned because they're keys don't allow it? As in, maybe this is desirable
in some situations?

> throw an error if the view query range can contain no rows
> ----------------------------------------------------------
>
>                 Key: COUCHDB-388
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-388
>             Project: CouchDB
>          Issue Type: Improvement
>    Affects Versions: 0.9
>            Reporter: Chris Anderson
>            Priority: Minor
>             Fix For: 0.11
>
>
> users get confused because when applying descending=true as a previously working query
will return 0 rows. this is correct behavior but we could make things a lot easier for people
if we'd raise an error in cases where its impossible for there to be keys between the start
and end.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message