The only solution to enforce uniqueness on a field is using the _id field of a document. If you need two fields to be unique in a database, you'll need to use two documents for that. In addition, in the distributed case, the only way to ensure uniqueness is eventually, after replication, through conflicts that show up if two nodes created the same "unique" id. Cheers Jan -- On 27 Mar 2010, at 20:41, faust 1111 wrote: > Why too documents? > But i have one issue User > i need only one document . > > i am interesting, how couch people do in real projects. > when they need two unique fields in document. > > > 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 >>> login >>> email >>> >>> 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 >>>>> email: unique >>>>> login: unique >>>>> >>>> >>>> You can only have 1 unique field per database. you implement it by using it as a docid, like >>>> >>>> { >>>> "_id" : "user:unique", >>>> ... >>>> } >>>> >>>> Chris >> >>