Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Message-ID: <634367118.1137119540741.JavaMail.jira@ajax.apache.org>
Date: Fri, 13 Jan 2006 03:32:20 +0100 (CET)
From: "Craig Russell (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Subject: [jira] Updated: (JDO-276) TCK maps BigInteger to BIGINT; should be
 NUMERIC(31)
In-Reply-To: <868207521.1137118400239.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/JDO-276?page=all ]

Craig Russell updated JDO-276:
------------------------------

    Attachment: biginteger.patch

This patch changes the schma.sql scripts. The columns mapped to BigDecimal fields are changed from BIGINT to NUMERIC(31). It also changes values for some of the fields to numbers greater than 2^64 in order to test that the values greater than Long values can be stored.


> TCK maps BigInteger to BIGINT; should be NUMERIC(31)
> ----------------------------------------------------
>
>          Key: JDO-276
>          URL: http://issues.apache.org/jira/browse/JDO-276
>      Project: JDO
>         Type: Bug
>   Components: tck20
>     Reporter: Craig Russell
>     Assignee: Craig Russell
>     Priority: Minor
>      Fix For: JDO 2 beta
>  Attachments: biginteger.patch
>
> The TCK maps values of fields of type BigInteger to Derby column type BIGINT which is actually 64 bit fixed precision (Java long). The BigInteger type should map to NUMERIC(31) that provides more than 64 bits of precision.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira