incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From go canal <goca...@yahoo.com>
Subject Re: how to work on multiple databases
Date Wed, 23 Sep 2009 09:55:46 GMT
thanks. 
I quickly google, saw two lounge projects. guess this one is for the partitioning solution
? That's very good, I am about to ask this feature .....

Is there a plan to merge this into CouchDB core ?

 rgds,
canal




________________________________
From: Chris Anderson <jchris@apache.org>
To: user@couchdb.apache.org
Sent: Wednesday, September 23, 2009 1:29:36 PM
Subject: Re: how to work on multiple databases

On Tue, Sep 22, 2009 at 8:03 PM, Nadav Samet <thesamet@gmail.com> wrote:
> The HTTP API works against one database at a time (at one http server). All
> libraries I have seen will let you talk to multiple databases, but don't
> have any functionality to send a single query to several databases and
> aggregate the results. (This kind of functionality is too
> application-specific to be in a general purpose library.)

The CouchDB-Lounge project has a query merging proxy which could be
adapted for this purpose.

> On Tue, Sep 22, 2009 at 7:51 PM, go canal <gocanal@yahoo.com> wrote:
>
>> Hello,
>> I am only one-day 'old' in the Couch world, CouchDB is really cool :-)
>> I have a lot of questions though, sorry if these had been already
>> answered...
>>
>> Are there APIs available for working on multiple databases ?
>>
>> Here is the use case/data model:
>>  * a CouchDB database for one project
>>    all project related documents are stored in the DB.
>>  * a user can participate in multiple projects
>>
>> let's say a user wants to display a list of his documents in all projects,
>> how do we support this ? Do I have to issue one query command for each
>> database then aggregate the result ?
>>
>> thanks
>> canal
>>
>>
>>
>>
>
>
>
>
> --
> Sincerely yours,
> Nadav
>



-- 
Chris Anderson
http://jchrisa.net
http://couch.io



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