Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CABvT1DEEbepPVf_OqnWiC4aSTBNZF4K++1GYGPhUC7RbqpS1Tw@mail.gmail.com>
References: 
 <CAAOi-OFMhQ0X3iEUC6T0fSdwJLV20Huj4tnJZBSfZ5Q5TtEx7g@mail.gmail.com>
 <CAN-3CBK4OQ5jJDa3ojfxkt=nN0OVpX8JnFUp21-AkgJzLTtN5g@mail.gmail.com>
 <CAAOi-OFWeYtZbLfLbsUV9Egk3j6kFtVa2t9urZu95KH3buLJdw@mail.gmail.com>
 <CAMiZLn07ru9fUgxsmtCsT2rG8ShfRrD=1bpLRN-f1YGG8athTA@mail.gmail.com>
 <CAAOi-OGEvWZrEkDyrxr1W0FKmA=Feso=smesQYU9_joARtSiqQ@mail.gmail.com>
 <CAN-3CBK3SCx7Y5K1oEC+XfzgY2B+-9_0c90m6npM9GkE_myu0g@mail.gmail.com>
 <003240CB-2132-439B-AD7D-6AFBB00DA352@apache.org>
 <CAAOi-OHiVWDuAM4DUjd1q7R7voNmC5Y7uCPziC8=1DHsAU27TA@mail.gmail.com>
 <CABvT1DH440h0CAmdpHd-o0bgpjiojGvQMnROfjChpSVb=47dTQ@mail.gmail.com>
 <CAAOi-OFZ2uXhfKyL9ROwki+43ccO_MGFA9Z5TTPPYuAoAcU5CQ@mail.gmail.com>
 <CABvT1DG4G32p9fc164OdLyCDh37-E8jXzkaF5GdNXECh3tENtw@mail.gmail.com>
 <CAHdjipJZtAvY5kO6ot_-FnFG3NxKVgUoeiUCsnbAbVEr3zhnVA@mail.gmail.com>
 <CABvT1DEEbepPVf_OqnWiC4aSTBNZF4K++1GYGPhUC7RbqpS1Tw@mail.gmail.com>
From: Daniel Gonzalez <gonvaled@gonvaled.com>
Date: Fri, 16 Mar 2012 16:39:16 +0100
Message-ID: 
 <CAAOi-OFME8=EQ1hng+S2ypqtKeWS6D-vV-1YZ_LSs052tKBPLA@mail.gmail.com>
Subject: Re: Size of couchdb documents
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Mar 16, 2012 at 4:30 PM, Robert Newson <rnewson@apache.org> wrote:
> Ah, thanks, that's good advice. You can still grab a bunch of the
> uuids from /_uuids and then use them, thus giving you good uuids and
> idempotency too.
>
> b.
>

Understood. But this would not solve the doc_id size problem, which in
my database with 22 million documents has a big effect. So I need to
generate a doc_id on the clien side with few characters. Which brings
me back to my originial question: could somebody produce a base64
dictionary which is "Erlang term ordered"?