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 BE0A1102FE for ; Mon, 9 Dec 2013 17:49:18 +0000 (UTC) Received: (qmail 41441 invoked by uid 500); 9 Dec 2013 17:49:16 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 41400 invoked by uid 500); 9 Dec 2013 17:49:13 -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 41391 invoked by uid 99); 9 Dec 2013 17:49:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Dec 2013 17:49:12 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of st.fankl.in@gmail.com designates 209.85.214.43 as permitted sender) Received: from [209.85.214.43] (HELO mail-bk0-f43.google.com) (209.85.214.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Dec 2013 17:49:07 +0000 Received: by mail-bk0-f43.google.com with SMTP id mz12so1507647bkb.16 for ; Mon, 09 Dec 2013 09:48:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Cvp4k/UC0JW0kr3EfIHv307MkFxtY5MwwQbYRwtuW4s=; b=wWDJmmtVqWMWZecUkV13TjBfU8HW7FNr/sKZ2qrCLS3A0DDy8CsKPt2ySAwUUBcnv0 W+xlDuG3LPd0pRojiv6EGbs1vTZlUuKhe7PDGY1oVk5zmkdf2hqYHdXlhu/rhHF0jyBN PAZQutL54gHEtoMd9MCaFoi0FTDfpvGA0h4fjg9ccl6HpOQHmTH59ItYufXFYIfwDAno g86EXLCcEniC7Nn0heJwzrcW72SRhSBO5590k2BCT9eZgslykGyw9ouFzVsxIo6siPiq yKgoQ1Gx3ZRtHmQOo/xjz9EilhIhdxhEOzYByvf0uNjMKeqTJxYRqrHiWs9ca/wbSh4j uU3Q== MIME-Version: 1.0 X-Received: by 10.205.16.69 with SMTP id px5mr3456959bkb.9.1386611325340; Mon, 09 Dec 2013 09:48:45 -0800 (PST) Received: by 10.204.225.207 with HTTP; Mon, 9 Dec 2013 09:48:45 -0800 (PST) In-Reply-To: References: Date: Mon, 9 Dec 2013 18:48:45 +0100 Message-ID: Subject: Re: public_field: make sub-field visible From: Stefan Klein To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=20cf301cbeb07d3ddb04ed1d9be3 X-Virus-Checked: Checked by ClamAV on apache.org --20cf301cbeb07d3ddb04ed1d9be3 Content-Type: text/plain; charset=ISO-8859-1 Sorry, hit send to fast. :( 2013/12/9 Stefan Klein > Hi couch users, > > i got some application specific data in my user documents and have to make > one of the fields visible to other users. > public_field works fine, for top level fields. I try to make a sub field > visible. > > { > "_id": "org.couchdb.user:someuser", > "_rev": "somerev", > "appData" : { > "field" : "should be visible", > "secretfield" : "should not be visible" > } > i tried [couch_httpd_auth] public_fields = appData.field and public_fields = appData[field] both didn't work, so i guess it is not possible and public_fields only work on top level fields? Thanks, Stefan --20cf301cbeb07d3ddb04ed1d9be3--