Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 39085 invoked from network); 3 Oct 2006 00:54:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Oct 2006 00:54:10 -0000 Received: (qmail 81791 invoked by uid 500); 3 Oct 2006 00:54:09 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 81565 invoked by uid 500); 3 Oct 2006 00:54:09 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 81556 invoked by uid 99); 3 Oct 2006 00:54:09 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Oct 2006 17:54:09 -0700 Authentication-Results: idunn.apache.osuosl.org header.from=home4slc@pacbell.net; domainkeys=good X-ASF-Spam-Status: No, hits=2.7 required=5.0 tests=DNS_FROM_RFC_WHOIS,NO_REAL_NAME,RCVD_IN_SORBS_WEB DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 Received: from [68.142.199.125] ([68.142.199.125:34675] helo=web81309.mail.mud.yahoo.com) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id 7D/B1-29668-7F2B1254 for ; Mon, 02 Oct 2006 17:46:48 -0700 Received: (qmail 47311 invoked by uid 60001); 3 Oct 2006 00:46:44 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=pacbell.net; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=Hrc4rFSaiyQ2cPrxF1W9qHC+47V+LfOAuJpbyZAwY53wCF3NxYz1fpIbIKDF68L3KfMNxr+wGolfq7lPnIP1rCL/pfkgMyyBA1LaNZcmlwwHlVXRLrL9qrbd3V6/haw4e0E2JUXMNGD+WwhLqhuJtRCN0VxtY9yHkSy/M7vvMBQ= ; Message-ID: <20061003004644.47309.qmail@web81309.mail.mud.yahoo.com> Received: from [32.97.110.142] by web81309.mail.mud.yahoo.com via HTTP; Mon, 02 Oct 2006 17:46:44 PDT Date: Mon, 2 Oct 2006 17:46:44 -0700 (PDT) From: Subject: Re: Numeric limitations in Derby - 'Largest decimal precision' To: derby-dev@db.apache.org In-Reply-To: <54ac72d70610020016s647553d5x1745d71976d6fb7d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Thanks Andrew. I updated the http://wiki.apache.org/db-derby/ReferenceManualTenTwo wiki page to reflect that this change needs to be made in the docs still. Susan ----- Original Message ---- From: Andrew McIntyre To: derby-dev@db.apache.org Sent: Monday, October 2, 2006 12:16:45 AM Subject: Re: Numeric limitations in Derby - 'Largest decimal precision' On 9/1/06, Susan Cline wrote: > In the Reference manual, http://db.apache.org/derby/docs/10.2/ref/rrefnumericlimits.html, > the 'Largest decimal precision' value is listed as 31,255. > > Shouldn't this be 31? Or is there some meaning to the 255 after the 31 that I don't understand? Clearing out some old mail... Correct. 31 is the greatest DECIMAL precision allowed. The value for scale should be less than the precision value. Derby certainly does not allow multiple thousands of digits of decimal precision, so this entry in the developer's guide appears to be incorrect. andrew