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 bchesneau@gmail.com
 designates 209.85.214.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <BANLkTi=SDOmR67ePv2wgE267LutGRomn5w@mail.gmail.com>
References: <7800EECA-326D-46C2-B283-E37636EBD2F4@mooseyard.com>
	<BANLkTi=AQa4153Cit3Sjfq+v6f3Kv=fd7Q@mail.gmail.com>
	<BANLkTi=SDOmR67ePv2wgE267LutGRomn5w@mail.gmail.com>
Date: Thu, 30 Jun 2011 09:35:31 +0200
Message-ID: <BANLkTi=xbGTHZKZrFnEW6CKv+7GjKQqKnQ@mail.gmail.com>
Subject: Re: Are server-generated doc IDs better?
From: Benoit Chesneau <bchesneau@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 30, 2011 at 3:08 AM, Dale Harvey <dale@arandomurl.com> wrote:
> CouchDB generates uuid's that attempts to minimise the amount of rebalanc=
ing
> that needs to happen on insert, however thats only an optimization I woul=
d
> worry about if you are under fairly severe load.
>
> If your application has natural id's then I would use them, if not then I
> think its fine to use POST as long as you aware of the idempotent issue
>
Other way is to get a bunch of uuids from couch and using them in your
PUT, so you don't have to generate yourself uuids. (and you have best
of both world).

- beno=EEt