[
https://issues.apache.org/jira/browse/COUCHDB-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635245#action_12635245
]
Chris Anderson commented on COUCHDB-124:
----------------------------------------
We discussed this on IRC - there's not a good reason to add this. See
http://wiki.apache.org/couchdb/ViewCollation for full documentation of the JSON
sort order.
In the case of the example given, there is no need for the 'ZZZZ' string, this
is equivalent and not hackish.
startkey=["tag_name"]&endkey=["tag_name", {}]
of course, this doesn't help with the case of
startkey="_design/"&endkey="_design/ZZZZZZZZZ"
which we see frequently. But there's no way a "special" value can help with a
string range, because we can't allow the special value *inside* the string
without opening a whole can of worms. If you didn't want to be hackish while
defining a string range you could use a super-high unicode character.
startkey="_design/"&endkey="_design/\u9999"
> 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.
