Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 28778 invoked from network); 23 Feb 2010 22:50:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Feb 2010 22:50:25 -0000 Received: (qmail 4035 invoked by uid 500); 23 Feb 2010 22:50:23 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 3986 invoked by uid 500); 23 Feb 2010 22:50:23 -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 3976 invoked by uid 99); 23 Feb 2010 22:50:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Feb 2010 22:50:23 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of seanhess@gmail.com designates 74.125.83.180 as permitted sender) Received: from [74.125.83.180] (HELO mail-pv0-f180.google.com) (74.125.83.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Feb 2010 22:50:16 +0000 Received: by pvc7 with SMTP id 7so521028pvc.11 for ; Tue, 23 Feb 2010 14:49:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:references:from:in-reply-to:mime-version:date :received:message-id:subject:to:content-type; bh=FmKcj+jmUhaJTiE1KEVuPi1Rimw8faYKgObQNp7Wz+E=; b=aYVLBteBkdv8/wpZ+buxbO3Qke2nPnxunQiu45yraA1lj0r5jwrF3G45eoB+rB2Zd3 9Dd4zGdogpEnZE/+bKQdy10eXj3lBJgB9KxYcis701jKuXM62IG46JqE0tK0embQ39Hb ztTSu3cCcCSH+ziP9IpnWr25xsii8d0t2JKI0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :content-type; b=cGcT78J5MQm0x+hRZuCeMQew2LqrtkEn6AdKPfWISY2XHG9uIBMAFNDROUhh80v53m w5kGwpF1fc75rdfTE8fH+V0k3vYxYlUuRkssoL4c+UMKkCQk4aGFvRk7sxdNNtK8irmw +1KkXFP7j/EwySCJNmKnDiWExWW3mIWSz41Qo= References: <21a5a18d1002231104h75eee414gf6bcf6e03a6d3403@mail.gmail.com> From: Sean Hess In-Reply-To: Mime-Version: 1.0 (iPhone Mail 7D11) Date: Tue, 23 Feb 2010 15:49:53 -0700 Received: by 10.140.55.6 with SMTP id d6mr3884563rva.140.1266965396234; Tue, 23 Feb 2010 14:49:56 -0800 (PST) Message-ID: <-683182627280217118@unknownmsgid> Subject: Re: Rename a database? To: "user@couchdb.apache.org" Content-Type: text/plain; charset=ISO-8859-1 I need the system to stay live the whole time, so the rename has to be nearly instantaneous. I do wish there was an http way to do it though. On Feb 23, 2010, at 3:42 PM, Nils Breunese wrote: > You could use the replication feature. imported_data is your live > database and you create new_imported_database for the import. Once > the import is done you drop the imported_data, create a fresh > imported_data database and replicate new_imported_database to > imported_data. Afterwards you can delete new_imported_database. This > does require more storage than renaming the database on the > filesystem level, but the replication method can be done entirely > via HTTP. > > Nils. > ________________________________________ > Van: Sean Clark Hess [seanhess@gmail.com] > Verzonden: dinsdag 23 februari 2010 20:04 > Aan: user@couchdb.apache.org > Onderwerp: Rename a database? > > I need to import vast amounts of data into a couch database every > night. The > company providing us the data does not provide a list of changes, so > we need > to regenerate everything from scratch. > > I was thinking that it would be nice if I could create a new > database in > couch, copy in all the new data, then rename them once it is done. > That way > my old data can stay live while the new data is importing. > > Is there a way to rename databases? So, I would have an > "imported_data" > database, create a "new_imported_database", then delete the old and > rename > the new when the import finished. > > Any other ideas? > > De informatie vervat in deze e-mail en meegezonden bijlagen is > uitsluitend bedoeld voor gebruik door de geadresseerde en kan > vertrouwelijke informatie bevatten. Openbaarmaking, > vermenigvuldiging, verspreiding en/of verstrekking van deze > informatie aan derden is voorbehouden aan geadresseerde. De VPRO > staat niet in voor de juiste en volledige overbrenging van de inhoud > van een verzonden e-mail, noch voor tijdige ontvangst daarvan.