incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nathan Stott <>
Subject Re: Sorting items by number of votes
Date Thu, 05 Nov 2009 18:53:47 GMT
Lists are capable of building up arbitrary data structures much like what a
client would have to do to sort it.  I don't know if there is some limit on
the memory usage that a list can have.  If there is I have not heard of it.
 Right now I'm using lists to do 'joins' of my multi-doc-type views. I
haven't thrown the sorting into the mix, but I've thought about giving it a
shot to see how it performs.

On Thu, Nov 5, 2009 at 12:47 PM, Daniel Truemper <> wrote:

>  Why would a list be any less efficient than sorting on the client side?
>>  You
>> could even use the view API to constrain the results sent to the list
>> where
>> appropriate.
> I did not want to say that a list is less efficient than sorting on the
> client side. But (again AFAIK) the list function can format the view's
> output in the order the view returns the values. So in Devon's case where he
> wants to sort the view by value instead of key, a list will not make any
> difference with respect to the sorting...
> Maybe I am wrong and the list function can sort by value...???
> Daniel

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message