Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-Id: <5BC50A6D-FB6F-4F48-ABEE-B3904C51F5C4@apache.org>
From: Jan Lehnardt <jan@apache.org>
To: couchdb-user@incubator.apache.org
In-Reply-To: <D60D2C95-D4DA-459A-8C4A-2A7F2DE786EE@raybeam.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: Re: mapping on a key that doesn't exist
Date: Wed, 14 May 2008 00:04:13 +0200
References: <D60D2C95-D4DA-459A-8C4A-2A7F2DE786EE@raybeam.com>


On May 13, 2008, at 23:19, Bob Briski wrote:

> I've found that I can't create a view with a key that includes a  
> document key that doesn't exist in all documents.
>
> I confused myself with that opening statement so here's an example  
> of what I'm talking about:
> http://pastie.caboo.se/196397

try http://pastie.caboo.se/196428

Hans Dieter is correct in his assessment that the js process bails out  
when trying to use an undefined value. (where as undefined !== null in  
javascript.


> I understand if this is the way it's supposed to work.  I also  
> understand that I can use an if statement to check if the key exists  
> in the document.  However, that means that if I change the schema of  
> future documents and I've written a previous view that doesn't check  
> for all of it's keys, those previous views cease to function.
>
> I thought that a large advantage of document databases is the  
> ability to change the schema of your documents and not cause  
> problems.  Is this not the case, or am I thinking of this incorrectly?
>
> Thanks,
> Bob