couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Fouché" <>
Subject Re: Sort by date and find by key
Date Tue, 13 Jan 2009 23:44:38 GMT
OK, that's what I was thinking. I currently have all my documents in
full-text search indexes. I guess I'll use CouchDB for storage and
some reduce functions to build dashboards, and not for my
"complicated" queries.
I don't want to load my indexes down with the document content. For
more efficiency, they would only contain the reverse indexes.

As far as I know, the _external process cannot return document ids to
CouchDB, so CouchDB returns the full document to the caller. Would you
recommend doing this on the cliend side ? Query the index, and then
query CouchDB with a bunch of keys ?


On Wed, Jan 14, 2009 at 12:28 AM, Dean Landolt <> wrote:
> On Tue, Jan 13, 2009 at 6:22 PM, Nicolas Fouché <>wrote:
>> So I have to run multiple queries, then have to mix the results by
>> date. I need to paginate on this final resultset, and knowing that I
>> deal with thousands of documents, the process seems really
>> complicated.
>> e.g show documents from only one view and not the others because the
>> document they returned have a date greater than the results of the
>> first view. And then have to keep track of every keys, to call views
>> with some startkey and endkey.
> It's really  just a mergesort -- nothing major, though given a large enough
> resultset it could get painful. Intertwingling couch with something like
> solr will give you more options for efficient query strategies.
> errrrr, is CouchDB compatible with my project needs ?
> The answer to that question is almost always going to be *probably*,
> depending on how creative you want to get.
View raw message