From derby-dev-return-31132-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Mon Oct 02 07:16:51 2006 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 15900 invoked from network); 2 Oct 2006 07:16:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Oct 2006 07:16:51 -0000 Received: (qmail 6361 invoked by uid 500); 2 Oct 2006 07:16:50 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 6334 invoked by uid 500); 2 Oct 2006 07:16:50 -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 6309 invoked by uid 99); 2 Oct 2006 07:16:50 -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 00:16:50 -0700 Authentication-Results: idunn.apache.osuosl.org header.from=mcintyre.a@gmail.com; domainkeys=good X-ASF-Spam-Status: No, hits=0.5 required=5.0 tests=DNS_FROM_RFC_ABUSE DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 Received: from [66.249.92.173] ([66.249.92.173:28717] helo=ug-out-1314.google.com) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id 6E/F1-16031-0ECB0254 for ; Mon, 02 Oct 2006 00:16:49 -0700 Received: by ug-out-1314.google.com with SMTP id g33so493231ugd for ; Mon, 02 Oct 2006 00:16:46 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=e3vP+US+nSFrZ6VglDrwhPi1FB8kqnqUPfBXtJnUASmXP5qhIUrTnoPksRUeOHaL9YCgu0lR83B3UogBlAgvwz2R414zeQr6CJl2PxWrYEFiDgCF+wrY26OLvIUDr+a1PFXrezaXG0E6/Y2cBioRGq7AfNqwSBVsMdCxZ8jrt6U= Received: by 10.66.224.3 with SMTP id w3mr2540464ugg; Mon, 02 Oct 2006 00:16:45 -0700 (PDT) Received: by 10.66.255.4 with HTTP; Mon, 2 Oct 2006 00:16:45 -0700 (PDT) Message-ID: <54ac72d70610020016s647553d5x1745d71976d6fb7d@mail.gmail.com> Date: Mon, 2 Oct 2006 00:16:45 -0700 From: "Andrew McIntyre" To: derby-dev@db.apache.org Subject: Re: Numeric limitations in Derby - 'Largest decimal precision' In-Reply-To: <20060901192833.30106.qmail@web81310.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060901192833.30106.qmail@web81310.mail.mud.yahoo.com> X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 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