[
https://issues.apache.org/jira/browse/COUCHDB-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Lehnardt closed COUCHDB-144.
--------------------------------
Resolution: Duplicate
Dupe of COUCHDB-158. Closing this because the later one has a patch attached.
Paul says this is non-blocking for 0.9 and low-priority for 1.0. But the patch
should be easy enough to integrate if somebody really needs this.
> Allow design docs to specify custom sort orders for composite keys
> ------------------------------------------------------------------
>
> Key: COUCHDB-144
> URL: https://issues.apache.org/jira/browse/COUCHDB-144
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Reporter: Nick Johnson
>
> Currently, there is no way to construct an index with different sort orders
> on different subkeys. For example, you might want to have a view of users
> sorted by city ascending, then age descending. With some data types this is
> easy enough to fudge by negating the values (eg, integers, floats, bools),
> but with strings this is currently practically impossible to achieve. I'm
> implementing a CouchDB interface for App Engine apps, and this issue is a
> blocker, preventing me from finishing it.
> From a conversation with damienkatz in IRC:
> <damienkatz> I was going to say it seems fine to add key array collation info
> the design docs
> <damienkatz> something like {key_array_collation:["asc", "desc", "desc"], ...}
> <damienkatz> create a new bug for it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
