[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-802) JBoss maps java.math.BigDecimal to numeric(19,2) for Firebird 1.5 DB. Firebird complains precision must be <= 18.

[Carlo de Wolf (JIRA)]

     [ http://jira.jboss.com/jira/browse/EJBTHREE-802?page=all ]

Carlo de Wolf resolved EJBTHREE-802.
------------------------------------

    Resolution: Rejected

For a BigDecimal field you must specify the precision and scale using the @Column annotation.
JSR 220: Enterprise JavaBeans(TM),Version 3.0, Final Release, 9.1.5 Column Annotation

> JBoss maps java.math.BigDecimal to numeric(19,2) for Firebird 1.5 DB.  Firebird complains precision must be <= 18.
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-802
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-802
>             Project: EJB 3.0
>          Issue Type: Bug
>         Environment: JBossAS-4.0.4.GA, Firebird 1.5, Fedora Core 5 Linux.
>            Reporter: knaveofhearts
>         Assigned To: Carlo de Wolf
>
> This is a problem with EJB 3 entity persistence with CMP.  I have several classes in which member variables are declared as BigDecimal.  The classes all work fine with HSQLDB, which I have been using for rapid development, using the create-drop capability.  I tried to switch the backend to Firebird 1.5 by changing the two relevant files (if I recall, persistence.xml and the []-ds.xml file), and managed to remove all the problems (e.g., Fireword reserve words like "role", "user", and "type" that I used as class or attribute names) except for BigDecimal fields.  The server log says that BigDecimal is being mapped to numeric(19,2), but the maximum precision for Firebird is 18.  If I replace all the BigDecimal fields with double, then my basic DB access tests run okay.  I have posted this problem to two JBoss forums (EJB3 and Persistence) and to one Firebird forum (Firebird-Java), but have gotten no replies.  If there is an easy fix, I would appreciate learning about it.

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