incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Anderson (JIRA)" <>
Subject [jira] Commented: (COUCHDB-124) Adding first and last sort keys
Date Sun, 28 Sep 2008 18:35:44 GMT


Chris Anderson commented on COUCHDB-124:

We discussed this on IRC - there's not a good reason to add this. See
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 


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.


> Adding first and last sort keys
> -------------------------------
>                 Key: COUCHDB-124
>                 URL:
>             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.

View raw message