[
https://issues.apache.org/jira/browse/COUCHDB-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997891#comment-12997891
]
Paul Joseph Davis commented on COUCHDB-1071:
--------------------------------------------
I would also point out two other things. While there is a "sequential" uuid
algorithm in CouchDB, it is still random and shouldn't significantly increase
the chances of a collision for small numbers of nodes in the replication
network. Sequential integer ids wouldn't maintain this property especially in a
cluster environment.
Also, if you mean to have doc id's that are integers (as opposed to strings
that represent integers) that'll not happen. Pretty much every part of CouchDB
requires _id's to be integers and switching them out would be fairly complex
and not overly general because of places that id's are expected to be (ie,
URL's).
> Integer UUIDS (1, 2, 3, ...)
> ----------------------------
>
> Key: COUCHDB-1071
> URL: https://issues.apache.org/jira/browse/COUCHDB-1071
> Project: CouchDB
> Issue Type: Improvement
> Components: Database Core
> Affects Versions: 1.0.2
> Environment: All
> Reporter: adisk
> Labels: algorithm, uuid
>
> Please, create integer uuids.
> What need:
> - intger keys
> - autogenerated by CouchDB
> - sequential
> Like a 1, 2, 3, 4, 5,...
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
