Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 26280 invoked from network); 23 Sep 2009 03:04:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Sep 2009 03:04:29 -0000 Received: (qmail 79143 invoked by uid 500); 23 Sep 2009 03:04:27 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 79063 invoked by uid 500); 23 Sep 2009 03:04:27 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 79052 invoked by uid 99); 23 Sep 2009 03:04:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Sep 2009 03:04:27 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of thesamet@gmail.com designates 74.125.92.27 as permitted sender) Received: from [74.125.92.27] (HELO qw-out-2122.google.com) (74.125.92.27) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Sep 2009 03:04:19 +0000 Received: by qw-out-2122.google.com with SMTP id 3so126501qwe.29 for ; Tue, 22 Sep 2009 20:03:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=wI4EqI+lG4LthUBLZr6WOz9YnUB0GzzKgfQ6T+Q0ZFg=; b=hrO565U6s7Oy3iH+cWyQ3tOyIuF9CoWfSsecAGHQJtm6JU6A8KlaQNHcMefOzHx6mS aonjy9T3VLKW8MGNtDjPrf17CA3bZvb7KyT/YFb5DoAkWnZZ142LQExPftTiws+i6MLH H9w4gClssp1v4WkBH2Vzp40/eQT7suw7t0RWM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=bEbD/7bWKhDpGYO2huvEFGVQlach3eb78I9GXvobqduyr+3oFXnQ45x/TV+hC7+7c3 jdnxIH2tIx1DTn8G1q9G7cl97QSMKgvQvDTySpPCwJWpizlb/27Xft/EW0vK9kyrFmGU QZ55xRGAMzFc+XxmJ4jBaFHCGU8UDlwi3bRss= MIME-Version: 1.0 Received: by 10.224.7.16 with SMTP id b16mr1468778qab.94.1253675038535; Tue, 22 Sep 2009 20:03:58 -0700 (PDT) In-Reply-To: <24941.65701.qm@web45306.mail.sp1.yahoo.com> References: <24941.65701.qm@web45306.mail.sp1.yahoo.com> Date: Tue, 22 Sep 2009 20:03:58 -0700 Message-ID: <8ffb00ae0909222003g3c1783d7i4d5e0cd6abd35593@mail.gmail.com> Subject: Re: how to work on multiple databases From: Nadav Samet To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=000feaf07ee755f06d047435f721 X-Virus-Checked: Checked by ClamAV on apache.org --000feaf07ee755f06d047435f721 Content-Type: text/plain; charset=ISO-8859-1 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.) On Tue, Sep 22, 2009 at 7:51 PM, go canal 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 --000feaf07ee755f06d047435f721--