couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilbert B Garza (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-124) Adding first and last sort keys
Date Sun, 28 Sep 2008 07:33:44 GMT

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

Gilbert B Garza commented on COUCHDB-124:
-----------------------------------------

I think this is a great idea. Perhaps something along the lines of _null could work, since
its meaning could be interpreted by its context.

> Adding first and last sort keys
> -------------------------------
>
>                 Key: COUCHDB-124
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-124
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>            Reporter: Paul Joseph Davis
>
> We should add values to the view query that are guranteed to be sorted first or last.
> Simple example, given an emitted key of something like [doc.tag, doc.descr] currently
to get the data for a specific tag we would use something like:
> startkey=['tag_name']&endkey=['tag_name', 'ZZZZZZ'] which is a bit hackish at best.
> Perhaps startkey=['tag_name',_first_]&endkey=['tag_name',_last_]
> Obviously _first_ and _last_ are crappy. And _first_ would even be optional. But hopefully
that conveys the idea.

-- 
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