Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 35029 invoked from network); 23 Feb 2010 19:25:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Feb 2010 19:25:02 -0000 Received: (qmail 64609 invoked by uid 500); 23 Feb 2010 19:25:00 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 64542 invoked by uid 500); 23 Feb 2010 19:25:00 -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 64532 invoked by uid 99); 23 Feb 2010 19:25:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Feb 2010 19:25:00 +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 (nike.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 19:24:52 +0000 Received: by pvc7 with SMTP id 7so452348pvc.11 for ; Tue, 23 Feb 2010 11:24:31 -0800 (PST) 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=hLfdrMUzrTmpYGMdVc46aVe3SMcFH8h0o2MCTu/1A/M=; b=hlhlN65xHKJEbmnS6aLyTBTc5MKKnU3qIuB2I3CQk7AFRuXH1CW/D1RmtlAmNVSnut 3BLBLTpwVOeVmF8a5ycRq6lcpSe+OC8nb4j0z7+G8gf9ARqJJWKe8nabQh5hJam+1HA2 E/Lg4rEZ6kOtP4a2qrjmj5hQh9AUb8hb4N7fQ= 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=B+LpZvFy9nnEc8PB8K9ZDZgk/aha584Tu00ml3jJIxE8PkBBu1dhzduAByZrSinysp q7z2jdvMZ14BelfnvN8fmIb6WCiVsyOOIPyLFL3d9H0Ro1+zPuawc9+sxPINax63+q5q SRu5Z7ty3tsIs+lZjVZWGhDz/2je5XYtli3j4= MIME-Version: 1.0 Received: by 10.141.125.3 with SMTP id c3mr3787344rvn.36.1266953070968; Tue, 23 Feb 2010 11:24:30 -0800 (PST) In-Reply-To: <98a246a11002231119s707098e7g9b1c842eba1b0067@mail.gmail.com> References: <21a5a18d1002231104h75eee414gf6bcf6e03a6d3403@mail.gmail.com> <98a246a11002231119ubef7fd4q5021c35c6e7afc0c@mail.gmail.com> <98a246a11002231119s707098e7g9b1c842eba1b0067@mail.gmail.com> Date: Tue, 23 Feb 2010 12:24:30 -0700 Message-ID: <21a5a18d1002231124l55a2d13ehe674ba162cd2af53@mail.gmail.com> Subject: Re: Rename a database? From: Sean Clark Hess To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=000325560f9ebe01470480497f1d X-Virus-Checked: Checked by ClamAV on apache.org --000325560f9ebe01470480497f1d Content-Type: text/plain; charset=ISO-8859-1 really? Where are the couch data files stored? (redhat) On Tue, Feb 23, 2010 at 12:19 PM, Metin Akat wrote: > Renaming the database file works. > Moving the file from one machine to another also works. > > On Tue, Feb 23, 2010 at 9:19 PM, Metin Akat wrote: > > On Tue, Feb 23, 2010 at 9:04 PM, Sean Clark Hess > wrote: > >> 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? > >> > > > --000325560f9ebe01470480497f1d--