Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 72411 invoked from network); 10 Oct 2010 09:44:33 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 10 Oct 2010 09:44:33 -0000 Received: (qmail 85110 invoked by uid 500); 10 Oct 2010 09:44:31 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 84713 invoked by uid 500); 10 Oct 2010 09:44:29 -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 84705 invoked by uid 99); 10 Oct 2010 09:44:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Oct 2010 09:44:28 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,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 sebastiancohnen@googlemail.com designates 209.85.214.52 as permitted sender) Received: from [209.85.214.52] (HELO mail-bw0-f52.google.com) (209.85.214.52) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Oct 2010 09:44:22 +0000 Received: by bwz13 with SMTP id 13so2195019bwz.11 for ; Sun, 10 Oct 2010 02:44:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:content-type:mime-version :subject:from:in-reply-to:date:content-transfer-encoding:message-id :references:to:x-mailer; bh=8EABxggTYS/T9mlwbVMbYzmMdDEkBNUYgQexoZqN/SU=; b=FOwEwm9yv4iANaDdn7UbIfI58KlpQ+StAmsoYIHJ/Nc+Uy40mUcyTmUZKpG9ggyHHr AfqxAo/XZikjnAE/CpyCqo+gGYed309iypOVq9LFra3Vl5iNyi1HiF7aBhRxMdM7Gw5X hcfiUXRmbGFrxow1UHEIb2DcNi5ICr2P3zDG8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=TfMd0Pn/mfOLBYxTHz3ZDZP/8LBLrUnnJvPkhS/DvRDSQ0Y/8Ps1s0JXwZGMt8Cydv JeysxhjcktY1OP5fKEg9xa8rpGBv09YO99FqHfSy8O1/FfYQ9rsG/gnrq4yyOOsbqqTO MYLCzb5KzkIRleOPrHma1XXiFXUEeHkuRJdew= Received: by 10.204.100.12 with SMTP id w12mr4101622bkn.90.1286703840622; Sun, 10 Oct 2010 02:44:00 -0700 (PDT) Received: from [192.168.178.21] (koln-5d81a25a.pool.mediaWays.net [93.129.162.90]) by mx.google.com with ESMTPS id a25sm2510678bks.20.2010.10.10.02.43.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 10 Oct 2010 02:43:59 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1081) Subject: Re: design doc weakness (one view fails = all views fail) From: Sebastian Cohnen In-Reply-To: <73295728.1269841286696237330.JavaMail.root@zimbra5-e1.priv.proxad.net> Date: Sun, 10 Oct 2010 11:43:57 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <6A4FE566-DA4B-4596-8517-91E17473B9FE@googlemail.com> References: <73295728.1269841286696237330.JavaMail.root@zimbra5-e1.priv.proxad.net> To: user@couchdb.apache.org X-Mailer: Apple Mail (2.1081) Hey Mickael, views are processed in together groups (one per design document). this = "weakness" is - AFAIK - not really avoidable in the current = architecture. On 10.10.2010, at 09:37, mickael.bailly@free.fr wrote: >=20 > Hello couchers, >=20 > it seems that, on a design document, if there is one view having an = error ( for example "Expression does not eval to a function" ) than all = other views are then unusable. > It's not critical and not a real bug, but from my point of view it's a = weakness : one error on one part of the design doc leads to a totally = broken app / couchapp. >=20 > Steps to reproduce :=20 >=20 > 1/ create a new database > 2/ Create a design doc : >=20 >=20 > { > "_id": "_design/doc1", > "views": { > "v1": { > "map": "function() {}" > }, > "v2": { > "map": "thefunction() {}" > } > }, > "language": "javascript" > } >=20 > 3/ Create a doc : >=20 > { > "_id": "doc1" > } >=20 > 4/ Call the "v1" view >=20 > What's your opinion on this ? Is it worth creating a Jira bug ? >=20 > Regards, >=20 > Mickael