From dev-return-15011-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Tue Feb 22 21:57:02 2011 Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 95919 invoked from network); 22 Feb 2011 21:57:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Feb 2011 21:57:02 -0000 Received: (qmail 62668 invoked by uid 500); 22 Feb 2011 21:57:01 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 62590 invoked by uid 500); 22 Feb 2011 21:57:01 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 62582 invoked by uid 99); 22 Feb 2011 21:57:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Feb 2011 21:57:01 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Feb 2011 21:56:59 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 80C9C1B2024 for ; Tue, 22 Feb 2011 21:56:38 +0000 (UTC) Date: Tue, 22 Feb 2011 21:56:38 +0000 (UTC) From: "Randall Leeds (JIRA)" To: dev@couchdb.apache.org Message-ID: <132074929.9370.1298411798523.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <655693008.7350.1298353178533.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] Commented: (COUCHDB-1071) Integer UUIDS (1, 2, 3, ...) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/COUCHDB-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998054#comment-12998054 ] Randall Leeds commented on COUCHDB-1071: ---------------------------------------- The update sequence is already somewhat similar. While documents don't "keep" a single update sequence (it changes if they're updated), this at least provides a monotonic, auto-incrementing id to each revision *on a particular server*. Using the /_changes feed might be all you need, depending on your use case. > 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