From user-return-16083-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Tue May 3 20:22:08 2011 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 4C9E72145 for ; Tue, 3 May 2011 20:22:08 +0000 (UTC) Received: (qmail 25668 invoked by uid 500); 3 May 2011 20:22:06 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 25590 invoked by uid 500); 3 May 2011 20:22:06 -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 Delivered-To: moderator for user@couchdb.apache.org Received: (qmail 13320 invoked by uid 99); 3 May 2011 14:39:40 -0000 X-ASF-Spam-Status: No, hits=0.8 required=5.0 tests=FS_REPLICA,HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of john.poyau@lmco.com designates 192.31.106.12 as permitted sender) Date: Tue, 03 May 2011 10:38:52 -0400 From: "Poyau, John" Subject: Document Timestamp On Replication To: "user@couchdb.apache.org" Message-id: <9946CE35511F1449ADF88A3F647DFE2816B0602907@HVXMSP8.us.lmco.com> MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_e+Znrm229eQWwHVvh0Z3pQ)" Content-language: en-US Thread-Topic: Document Timestamp On Replication Thread-Index: AcwERRFKH6FXYN1HQI6vi8lGVYtyPg== Accept-Language: en-US acceptlanguage: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15,1.0.148,0.0.0000 definitions=2011-05-03_04:2011-05-03,2011-05-03,1970-01-01 signatures=0 X-Virus-Checked: Checked by ClamAV on apache.org --Boundary_(ID_e+Znrm229eQWwHVvh0Z3pQ) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Hi All, Our project the learningregistry is using couchdb and we are trying to figure out what is the best way to update document timestamps on replication. Currently we have a resource_data database where resource_data document has a update_timestamp field that is set when the document is pushed to database and any time that the document is updated thereafter. We want the update_timestamp to be time of replication when the document gets replicated. What is the couchdb way of update the documents update_timestamp on replication. --Boundary_(ID_e+Znrm229eQWwHVvh0Z3pQ)--