Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <12284297.175771290090914496.JavaMail.jira@thor>
Date: Thu, 18 Nov 2010 09:35:14 -0500 (EST)
From: "Robert Newson (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Created: (COUCHDB-956) Return all _seq values as strings not
 integers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Return all _seq values as strings not integers
----------------------------------------------

                 Key: COUCHDB-956
                 URL: https://issues.apache.org/jira/browse/COUCHDB-956
             Project: CouchDB
          Issue Type: Improvement
            Reporter: Robert Newson


Some fields are returned as strings in db_info and other places to protect against numeric overflow;

{"db_name":"db","doc_count":0,"doc_del_count":0,"update_seq":0,"purge_seq":0,"compact_running":false,"disk_size":79,"instance_start_time":"1290088043619158","disk_format_version":5,"committed_update_seq":0}

here, instance_start_time is protected but, more critically, update_seq is not.

If update_seq were to be wrapped due to precision issues, what breaks?


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.