From user-return-8162-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Sun Dec 27 16:34:47 2009 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 72549 invoked from network); 27 Dec 2009 16:34:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Dec 2009 16:34:47 -0000 Received: (qmail 75305 invoked by uid 500); 27 Dec 2009 16:34:46 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 75230 invoked by uid 500); 27 Dec 2009 16:34:45 -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 75220 invoked by uid 99); 27 Dec 2009 16:34:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Dec 2009 16:34:45 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=FS_REPLICA,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [88.198.68.110] (HELO mail01.2flub.org) (88.198.68.110) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Dec 2009 16:34:37 +0000 Received: by mail01.2flub.org (Postfix, from userid 33) id 528F2664008; Sun, 27 Dec 2009 17:38:32 +0100 (CET) To: User Subject: Questions on replication (how to prevent DELETEs and resync deleted documents) MIME-Version: 1.0 Date: Sun, 27 Dec 2009 17:38:32 +0100 From: fana Message-ID: <08f6947cc76f5215f0d7a077c1181fbd@localhost> X-Sender: fana@2flub.org User-Agent: RoundCube Webmail/0.2.2 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" X-Virus-Checked: Checked by ClamAV on apache.org Hi, yesterday I played around with CouchDB's (0.10) replication feature. I have a database which should be something like a "master". Means, I want to replicate its complete content to other databases and from them all content back to the master. But I want to prevent documents to be deleted on the master which have (accidentally or not) been deleted on one of the other databases. I also want the master to resync the documents which were deleted on the other databases. After playing around and reading the documentation I found that deleted documents get only resynced again if the revision was changed so the document appears in the "_changes" resource. Is it somehow possible to build a scenario like this? So, * How can I resync deleted documents without touching the doument and getting a new revision? * How can I prevent documents to be deleted and only integrate new or changed documents to the master? Thanks in advance