Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 1364 invoked from network); 30 Mar 2010 14:14:12 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Mar 2010 14:14:12 -0000 Received: (qmail 63911 invoked by uid 500); 30 Mar 2010 14:14:11 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 63875 invoked by uid 500); 30 Mar 2010 14:14:11 -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 63867 invoked by uid 99); 30 Mar 2010 14:14:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Mar 2010 14:14:11 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of faust451@gmail.com designates 72.14.220.158 as permitted sender) Received: from [72.14.220.158] (HELO fg-out-1718.google.com) (72.14.220.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Mar 2010 14:14:03 +0000 Received: by fg-out-1718.google.com with SMTP id d23so105866fga.5 for ; Tue, 30 Mar 2010 07:13:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type :content-transfer-encoding; bh=AowRGqVT9H6rtGGodFM1O5I8NSmar258m+V3pvMl9I4=; b=wlvTwhvkNhobsozC3VbkXeYlbY21QR5D7Ks3OY9VjkGBn0LLb0ZFaiARHKJneI558R AVjEdLQohBimfEm4ZL4vwz30tAOqf1CbSrDrb+zErd6XNO/Uu9KY9Xch9JFbxYJVJyP0 sHmRSCo8r/rAxyjhflsLKwHoPHDjM6Jfi/oI0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=YetBAR+jn8HBYCSDLL5decp7A7felVtPxm4YOvThH2R0jC0BIKeJP8iorkEQnukIS3 3kTrEvBYm1B3//3dmrXXhGeny1wim7dHCk4BYUmeEvLTb5zmDry9qc2oxPsBg0XLyHM7 Hddr+1JhvnP/nvNPKY5ClCFWGIGowCLColTPg= MIME-Version: 1.0 Received: by 10.86.51.16 with HTTP; Tue, 30 Mar 2010 07:13:42 -0700 (PDT) In-Reply-To: References: <91076E76-9FAB-4590-82E2-9B14563882F0@gmail.com> Date: Tue, 30 Mar 2010 18:13:42 +0400 Received: by 10.87.62.39 with SMTP id p39mr4890176fgk.9.1269958422799; Tue, 30 Mar 2010 07:13:42 -0700 (PDT) Message-ID: Subject: Re: Validate uniqueness field From: faust 1111 To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org It's very frightful for me implement uniqueness in this way create doc for each uniq field and keep it in actual state when i update do= cs. may be better check uniqueness only in application layer? now i don't think about distribute. 2010/3/28 Jan Lehnardt : > You need to have two documents with a unique ID each. > > Cheers > Jan > -- > > On 27 Mar 2010, at 17:12, faust 1111 wrote: > >> but what if i have two unique fields >> =A0login >> =A0email >> >> 2010/3/28 J Chris Anderson : >>> >>> On Mar 27, 2010, at 4:56 PM, faust 1111 wrote: >>> >>>> Hi >>>> >>>> In what way i cat implement validation of uniqueness? >>>> User >>>> =A0email: unique >>>> =A0login: =A0unique >>>> >>> >>> You can only have 1 unique field per database. you implement it by usin= g it as a docid, like >>> >>> { >>> "_id" : "user:unique", >>> =A0 ... >>> } >>> >>> Chris > >