Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D61742931 for ; Tue, 3 May 2011 20:39:23 +0000 (UTC) Received: (qmail 57255 invoked by uid 500); 3 May 2011 20:39:22 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 57226 invoked by uid 500); 3 May 2011 20:39:22 -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 57218 invoked by uid 99); 3 May 2011 20:39:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 May 2011 20:39:22 +0000 X-ASF-Spam-Status: No, hits=3.6 required=5.0 tests=FS_REPLICA,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of omarshall@facilityone.com designates 216.135.43.146 as permitted sender) Received: from [216.135.43.146] (HELO secure.facilityone.com) (216.135.43.146) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 May 2011 20:39:17 +0000 Received: from [192.168.10.152] ([216.135.43.146]) (authenticated user omarshall@facilityone.com) by secure.facilityone.com (Kerio Connect 7.1.3) (using TLSv1/SSLv3 with cipher AES256-SHA (256 bits)); Tue, 3 May 2011 16:38:56 -0400 Message-ID: <4DC067DD.5070508@facilityone.com> Date: Tue, 03 May 2011 16:38:53 -0400 From: Owen Marshall User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: user@couchdb.apache.org CC: "Poyau, John" Subject: Re: Document Timestamp On Replication References: <9946CE35511F1449ADF88A3F647DFE2816B0602907@HVXMSP8.us.lmco.com> In-Reply-To: <9946CE35511F1449ADF88A3F647DFE2816B0602907@HVXMSP8.us.lmco.com> X-Enigmail-Version: 1.1.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigD538BA967F3B9C3CDBFD1447" --------------enigD538BA967F3B9C3CDBFD1447 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 05/03/2011 10:38 AM, Poyau, John wrote: > What is the couchdb way of update the documents update_timestamp on rep= lication. Are you using continuous replication? If so, _don't ever do this_! If you do, you will likely end up passing the same document back and forth between nodes. I.E: User pushes doc to node A, node A replicates to node B, node B bumps the update_timestamp, node A pulls the new document, node A bumps the update_timestamp... repeat ad nauseum. Even if you aren't using continuous replication, you still _shouldn't do this_! Replicate your documents and handle conflicts when they happen. If for some reason you have a truly good reason, you might be able to accomplish this with update handlers: http://wiki.apache.org/couchdb/Document_Update_Handlers But if you are not 100% completely positively sure, I'd urge you to read the excellent CouchDB guide on replication and on conflicts: http://guide.couchdb.org/draft/replication.html http://guide.couchdb.org/draft/conflicts.html --=20 Owen Marshall FacilityONE omarshall@facilityone.com | (502) 805-2126 --------------enigD538BA967F3B9C3CDBFD1447 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3AZ98ACgkQcoY1cxL6GH0wfACcDofXtBrE4vaFDYPzodt7OFD2 wpkAn0xM7ZSHfM+j4B8MCOF3f+wOY8gi =hhrL -----END PGP SIGNATURE----- --------------enigD538BA967F3B9C3CDBFD1447--