Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of awolff@gmail.com designates
 74.125.92.25 as permitted sender)
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;
        b=bN6PT6IJPCTw6t03Yw9hahKRxp/NCQDvknEf2TvrmSVAmkBf6zgS5Qf3D9SoOEXX4q
         9j8ck24ysjZfgTe1nGvMdB/JCcxgohsrMXcehQe/3tnjr4H/PxEgdwnWOZ+tiXze7DvO
         JM5Q2FmVSUtgLyclhQJt8P3Ptcpv0J7pmIgSg=
MIME-Version: 1.0
In-Reply-To: <55047b710907282033y6dd4624of96fd9b3fd90cc88@mail.gmail.com>
References: <55047b710907282033y6dd4624of96fd9b3fd90cc88@mail.gmail.com>
Date: Wed, 29 Jul 2009 14:03:37 -0700
Message-ID: <e8d26ac40907291403gae23b0dq2b48610c616070e9@mail.gmail.com>
Subject: Re: Unique human readable ID
From: Adam Wolff <awolff@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=001636426cd55361d9046fde85cc

--001636426cd55361d9046fde85cc
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

We are handling this by generating 128 bit random numbers (same amount of
data in a UUID) and then mapping them to 22 character strings, where the
first two characters are hex and the next 20 are base 64 (using
uppercase+lowercase+10 digits+"_"+"-" = 64 possible characters.)So 2^4 + 2^4
+ 20 * 2^6 = 128 bits
These could be trivially converted back to UUIDs.

Not a lot better than 36 character UUIDs, but a little.

A

On Tue, Jul 28, 2009 at 8:33 PM, Nicholas Orr <nicholas.orr@zxgen.net>wrote:

> I get the whole point of letting couchdb generate id's.
> At the same time I need a way to create a human
> memorable/readable/communicative id:
>  - ID: 45060, 45061, 45062, etc
> That is a whole lot simpler to relay over a phone call compared to:
> - 1d98d82f5b6a628527344ba991cb7e2f
>
> What have people done to satisfy the users of their systems with a simple
> id
> and also be able to replicate the documents between different couchdb
> instances?
>
> I've come up with 2 ideas:
>
> # 1
> Have a single couchdb that has 50 documents (tickets) (figure out a way to
> always have 50 available) in it like what is mentioned in the wiki to do
> transactions[1]
>
> #2
> For each instance of the application prefix the id with it's instance id so
> 1.45060 & 2.45060 have the same id but were created on different instances.
> Therefore when the two instances of the couchdb's replicate with each other
> there are two unique id's
> I can see this adding a fair amount of overhead if it gets to the point of
> more then a few instances...
>
> If I drop the requirement of replication everything becomes simple. Then I
> have to wonder - why am I using CouchDB then??
>
> Nick
>
>
> [1] -
> http://wiki.apache.org/couchdb/Frequently_asked_questions#transactions
>

--001636426cd55361d9046fde85cc--