From user-return-16431-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Wed Jun 1 07:07:28 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 BFAF0633F for ; Wed, 1 Jun 2011 07:07:28 +0000 (UTC) Received: (qmail 12213 invoked by uid 500); 1 Jun 2011 07:07:26 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 12178 invoked by uid 500); 1 Jun 2011 07:07:21 -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 12170 invoked by uid 99); 1 Jun 2011 07:07:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jun 2011 07:07:20 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of pixelsallover@gmail.com designates 74.125.82.54 as permitted sender) Received: from [74.125.82.54] (HELO mail-ww0-f54.google.com) (74.125.82.54) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jun 2011 07:07:12 +0000 Received: by wwd20 with SMTP id 20so5124312wwd.23 for ; Wed, 01 Jun 2011 00:06:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=UsiNAZ6ktX21QcyLpseYWZayHHlePXTcNtjCWFV2dMg=; b=C2l5tXZ8qtHUsWsXmRoM6JeJq5Zi5c4QrTU4lALH8VBiAcHc4bwLcWsWgzg4zxoQ7A 4ZXDQokakvLazi0aclqSAiwJSOJmLDeOz6VI2+tthyF3xAYw2YEpfJvobS1Y6KHJ2Fh3 JVqorS03VnQ3QSIi+aWedrEvrZh2J/QPEV1wU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=L93QqXhmCDzXgt/qKwGqnWVh8tJjkgkGocBsefUDoyjFaJkBwVmwr861hdykATkjUO rVsoe+ugGCmFKwQSdVVoWB3u9rUZkSm1AimUbN7QAmmfJ5oVG3xpLRT3JA++fHoRi5du q3NsF4sDQWUlUWEG1mQXu9Rs3aUjqBPkgV+1s= Received: by 10.216.140.147 with SMTP id e19mr6787895wej.49.1306912012114; Wed, 01 Jun 2011 00:06:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.180.129 with HTTP; Wed, 1 Jun 2011 00:06:32 -0700 (PDT) In-Reply-To: References: From: Anup Bishnoi Date: Wed, 1 Jun 2011 12:36:32 +0530 Message-ID: Subject: Re: attachments access in validate_doc_update? To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=0016e6dd8d673c1aa804a4a12aa6 X-Virus-Checked: Checked by ClamAV on apache.org --0016e6dd8d673c1aa804a4a12aa6 Content-Type: text/plain; charset=ISO-8859-1 What I mean is, can I access a doc's attachments inside the validate_doc_update function? On Mon, May 30, 2011 at 8:16 PM, Anup Bishnoi wrote: > Is it possible to access and validate attachments on a doc using > validate_doc_update? > Or, to use the attachments for the purpose of validation? > --0016e6dd8d673c1aa804a4a12aa6--