Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 85684 invoked from network); 5 Mar 2010 16:08:47 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Mar 2010 16:08:47 -0000 Received: (qmail 58799 invoked by uid 500); 5 Mar 2010 16:08:32 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 58756 invoked by uid 500); 5 Mar 2010 16:08:32 -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 58748 invoked by uid 99); 5 Mar 2010 16:08:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Mar 2010 16:08:32 +0000 X-ASF-Spam-Status: No, hits=1.0 required=10.0 tests=FREEMAIL_FROM,KHOP_SC_TOP_CIDR8,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mirko.kiefer@arcor.de designates 151.189.21.41 as permitted sender) Received: from [151.189.21.41] (HELO mail-in-01.arcor-online.net) (151.189.21.41) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Mar 2010 16:08:31 +0000 Received: from mail-in-09-z2.arcor-online.net (mail-in-09-z2.arcor-online.net [151.189.8.21]) by mx.arcor.de (Postfix) with ESMTP id E64993329AE for ; Fri, 5 Mar 2010 17:08:09 +0100 (CET) Received: from mail-in-07.arcor-online.net (mail-in-07.arcor-online.net [151.189.21.47]) by mail-in-09-z2.arcor-online.net (Postfix) with ESMTP id CFA012DE952 for ; Fri, 5 Mar 2010 17:08:09 +0100 (CET) Received: from mirko.fritz.box (mnhm-5f75dd00.pool.mediaWays.net [95.117.221.0]) (Authenticated sender: mirko.kiefer@arcor.de) by mail-in-07.arcor-online.net (Postfix) with ESMTPA id A24773CA352 for ; Fri, 5 Mar 2010 17:08:09 +0100 (CET) X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-07.arcor-online.net A24773CA352 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arcor.de; s=mail-in; t=1267805289; bh=7IoXeiG8LqQLo/k/icwRGFUM334muJNeBQBasAxnxpc=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date: Content-Transfer-Encoding:Message-Id:References:To; b=dB/oVp6YFq5r5V86xn6ruutYbcJamE9G3rotYhTjKE6LZe3XAw0mVHtBpYQyNqmAi 44uhFVFJFN8yuVOOgPnfkHHhJ3G6aUmvUxU3BCN5H2RO3j253hdSdrExTXaM83CStg wprw8Y1Fq+KVxUn2KYk556xNLo02gluvLUJA3W48= Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1077) Subject: Re: parsing JSON in update function From: Mirko Kiefer In-Reply-To: <33bc4c3c1003050725h53db4c08yfe2d48ca085c67d1@mail.gmail.com> Date: Fri, 5 Mar 2010 17:08:08 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <2EF500C3-64CC-4761-90C3-15563E0CFA40@arcor.de> References: <01C628E0-B3B7-4DCB-8834-78BCC4232208@arcor.de> <20100305085613.GA12132@uk.tiscali.com> <1C76E9CC-6899-441E-9750-6E2E94616E58@arcor.de> <33bc4c3c1003050725h53db4c08yfe2d48ca085c67d1@mail.gmail.com> To: user@couchdb.apache.org X-Mailer: Apple Mail (2.1077) Thanks Jim, this thread solved my problem! On Mar 5, 2010, at 4:25 PM, Jim Garvin wrote: > Hi Mirko, >=20 > I had this exact same issue a few days back. See this thread: >=20 > = http://mail-archives.apache.org/mod_mbox/couchdb-user/201003.mbox/<33bc4c3= c1003011453p6815da72t5b3c5f419999522f@mail.gmail.com> >=20 > I'm not sure if there's a better way to reference threads from this = list. > Anyways, that thread has me ultimately getting JSON.parse() to be = available > in the _udpate handlers and also dealing with a goofy issue when = upgrading > CouchDB without `make uninstall`ing the earlier version first. >=20 > Regards, > Jim >=20 > On Fri, Mar 5, 2010 at 5:27 AM, Mirko Kiefer = wrote: >=20 >>=20 >> On Mar 5, 2010, at 9:56 AM, Brian Candler wrote: >>=20 >>> On Fri, Mar 05, 2010 at 12:38:22PM +0900, km wrote: >>>> Hi, >>>>=20 >>>> Native JSON parsing is available in latest browsers like firefox = 3.1+ >> and IE >>>> 8 and others. >>>> so check if ur using latest browser versions. >>>=20 >>> I think he is talking about Javascript running server-side in = couchdb, >> not >>> in the client. >>>=20 >>> It depends which Spidermonkey couchdb was built with. In trunk it = now >> adds >>> JSON into the sandbox for those implementations which don't have a = native >>> JSON, so he should be OK when 0.11 is out. >>=20 >> Thanks, that sounds good! Yes, I'm talking about an update function = in a >> CouchDB design document which is executed on the server. >> I wonder what CouchDB uses internally to parse the docs to JSON?