You can fully randomized uuids by changing from 'sequential' to
'random' but, yes, the shared prefix is a compromise between random
uuids and values that play nicely with a b+tree.
B.
On 30 June 2011 20:04, Jens Alfke wrote:
>
> On Jun 30, 2011, at 12:35 AM, Benoit Chesneau wrote:
>
>> Other way
On Jun 30, 2011, at 12:35 AM, Benoit Chesneau wrote:
> 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).
Yes, but it’s much simpler (and faster) to call CFUUIDCreate() rather than
writ
On Thu, Jun 30, 2011 at 00:35, Benoit Chesneau wrote:
> On Thu, Jun 30, 2011 at 3:08 AM, Dale Harvey wrote:
>> CouchDB generates uuid's that attempts to minimise the amount of rebalancing
>> that needs to happen on insert, however thats only an optimization I would
>> worry about if you are under
On Thu, Jun 30, 2011 at 3:08 AM, Dale Harvey wrote:
> CouchDB generates uuid's that attempts to minimise the amount of rebalancing
> that needs to happen on insert, however thats only an optimization I would
> worry about if you are under fairly severe load.
>
> If your application has natural id'
On Thu, Jun 30, 2011 at 8:08 AM, Dale Harvey wrote:
> I
> think its fine to use POST as long as you aware of the idempotent issue
IMHO:
PUT is more informative in client logs
PUT is more informative in server logs
PUT is harder to screw up, because you front-load the hard part:
getting some ids
CouchDB generates uuid's that attempts to minimise the amount of rebalancing
that needs to happen on insert, however thats only an optimization I would
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 P
I had to patch jquery.couch.js that comes with couch to use post. It
was using a synchronous ajax call to get uuids which is a big no-no,
especially since I am using the same code on node.
On Sun, Jun 26, 2011 at 2:25 PM, Jens Alfke wrote:
> If my client code has access to a ready supply of uniq
If my client code has access to a ready supply of unique ID strings (in my
case, Cocoa’s CFUUID API), is there any disadvantage to using those to create
document IDs, versus using IDs generated by the server’s /_uuids endpoint?
On a similar note, if I’m talking to a server on localhost (from a
