Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of phrosty@gmail.com designates
 209.85.216.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=Tp41YidHN3icYoduqlAFyofOrUlQwYbxZADx5vhWvnik3lCSxE3XN0ckrLc5o8MJZZ
         aBXAWE+IGJrPMzSuOXKKSE2TOkhm1kpKuCbcMiCKan7RojWQg9xtOYLsqiOrsfT24kTI
         ilvpmFRsSD4g6bdbxq2WmuIP2CXrBV/W2FF00=
MIME-Version: 1.0
Date: Wed, 11 Nov 2009 17:00:34 -0800
Message-ID: <9b1d06140911111700k43d3f23eob40bf63fd1d43521@mail.gmail.com>
Subject: Ensuring unique attributes across documents?
From: Cory Nelson <phrosty@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8

Hello,

I'm trying to implement a typical user signup operation: when you
finally add a user to the database, you want it to have both a unique
user name, and a unique email.  In SQL I'd do something like:

BEGIN TRANSACTION ISOLATION LEVEL SERIALIZABLE

count = SELECT COUNT(*) FROM t_users WHERE name=? OR email=?

if(count == 0)
{
INSERT INTO t_users VALUES(...)
COMMIT
}
else
{
ROLLBACK
}

Can anyone give an example of how to achieve the same thing in CouchDB?

-- 
Cory Nelson