Andreas Borg commented on OPENJPA-2671:

I am using HSQLDB 2.3.3. Our specific problem is that 
{{Double.NEGATIVE_INFINITY}} (this probably also applies to 
{{POSITIVE-INFINITY}}) cannot be saved when a {{NUMERIC}} column is used (HSQL 
raises an exception saying "numeric value out of range". This problem does not 
ocur when enforcing a {{DOUBLE}} column by annotating 
{{@Column(columnDefinition = "DOUBLE")}}. I have attached test code (executable 
with {{mvn test}}), which reproduces this error and demonstrates that it does 
not occur with mapping to database type {{DOUBLE}}.

> Wrong type mapping for double in HSQLDB
> ---------------------------------------
>                 Key: OPENJPA-2671
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2671
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 2.4.1
>            Reporter: Andreas Borg
>         Attachments: testHsqldbDouble.zip
> Currently, Java type {{double}} is mapped to {{NUMERIC}} for HSQLDB:
> {code:title=HSQLDictionary.java, line 82|borderStyle=solid}
>        doubleTypeName = "NUMERIC";
> {code}
> (see 
> https://fisheye6.atlassian.com/browse/~tag=2.4.1/openjpa/tags/2.4.1/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/sql/HSQLDictionary.java?hb=true).
> This seems wrong to me, as HSQLDB's {{NUMERIC}} is not a binary floating 
> point type, but represents exact decimal numbers and maps to Java type 
> {{BigDecimal}} (see HSQL documentation: 
> http://hsqldb.org/doc/2.0/guide/sqlgeneral-chapt.html#sgc_numeric_types). The 
> corresponding HSQL type for {{double}} is, according to this manual, 
> {{REAL}}, {{FLOAT}} or {{DOUBLE}} (all being equivalent).

This message was sent by Atlassian JIRA

Reply via email to