couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ronny Pfannschmidt (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1498) range_prefix view parameter to ease working with ranges
Date Mon, 18 Jun 2012 16:07:42 GMT

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

Ronny Pfannschmidt commented on COUCHDB-1498:
---------------------------------------------

the main issue is - that from what i gathered - all wrong key prefixes are used out there,
to supposedly mean what i want to archieve
i suppose its reasonable to assume to do this only for one level of nesting (only work for
string key and array key, don’t consider partial of the last item(

i still would like to propose both variants, 

keyprefix would be strict, and consider only items in the toplevel sequence (so it would work
for strings and arrays and solve most simple cases)
rangeprefix would recurse on the last item of the sequence if it is a array or string

but im under the impression that the rangeprefix idea is a bit too complicated and may cause
grief in the long run
                
> range_prefix view parameter to ease working with ranges
> -------------------------------------------------------
>
>                 Key: COUCHDB-1498
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1498
>             Project: CouchDB
>          Issue Type: Bug
>          Components: View Server Support
>            Reporter: Ronny Pfannschmidt
>
> queries for certain ranges are a common operation,
> but we are usually left with figuring what kind of start/end key combination to use if
we want a certain range
> it would be really pleasant if instead of constructing a start/end range from a prefix
by guessing mostly how to construct the end param,
> we could just pass the range prefix as a string/array to the view

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message