Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 64897 invoked from network); 14 Jan 2009 02:43:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Jan 2009 02:43:02 -0000 Received: (qmail 65829 invoked by uid 500); 14 Jan 2009 02:42:56 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 65791 invoked by uid 500); 14 Jan 2009 02:42:56 -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 65780 invoked by uid 99); 14 Jan 2009 02:42:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jan 2009 18:42:56 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of thesunny@gmail.com designates 209.85.198.225 as permitted sender) Received: from [209.85.198.225] (HELO rv-out-0506.google.com) (209.85.198.225) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jan 2009 02:42:49 +0000 Received: by rv-out-0506.google.com with SMTP id g37so313623rvb.35 for ; Tue, 13 Jan 2009 18:42:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=kmCXJK9e3/m8WjZjC3DE9WFXlykNPkGfJtYag3m1wBY=; b=jzieeJ7x9KNkN6QoNpdhzWGfq1to85092HuT95lyRVe6a6O9NEmtAhwswHVCLuoprD +xA8BvU9dt7O+FdNODKBKGHBqvJGGJzlJ7+74jfep1qZeY5PXtWGoto5byjR17JICy9X mmIQaublDsVm1PWQGym4y4RHexexKyQJMbt+s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=p5j64ydQBw5ocE20kaaYt+ioeJwCpv6hM/Hq51MCbX1telVMTyuEFBtnmuEoPEriq8 /+7qYn1MEQg7+N7tTgSsz2M/20RESoUB81dXCAxKuSocgTFHjMfmS5rt5vBG3GvaPloM yh+SiCQrmOOTaoRjN1UXNAnk78VURMM0txWFI= Received: by 10.140.125.19 with SMTP id x19mr1940684rvc.187.1231900949502; Tue, 13 Jan 2009 18:42:29 -0800 (PST) Received: by 10.140.163.9 with HTTP; Tue, 13 Jan 2009 18:42:29 -0800 (PST) Message-ID: <518815b70901131842u5ad900c6gcc5e97dd73a936a3@mail.gmail.com> Date: Tue, 13 Jan 2009 18:42:29 -0800 From: "Sunny Hirai" To: user@couchdb.apache.org Subject: Re: Can I guarantee uniqueness in a field without using _id? In-Reply-To: <482703BB-BBA1-4565-BF8A-2CAFCA190001@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_90751_4019036.1231900949491" References: <518815b70901111530o23f6ce31yb40f974ea85467c0@mail.gmail.com> <791F7A73-DB3B-4822-8D93-A904802A427A@gmail.com> <482703BB-BBA1-4565-BF8A-2CAFCA190001@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_90751_4019036.1231900949491 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Ara.T.Howard and Antony Blakey: Thanks for the feedback. Hmm, this idea is interesting assuming that CouchDB will enforce the uniqueness per database (see earlier post I made). I think I will consider this. In-ter-esting. Sunny ------=_Part_90751_4019036.1231900949491--