You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/04/04 11:53:00 UTC
[jira] [Commented] (OPENJPA-2859) [HSQLDB] HSQLDictionary wrongly
maps double to NUMERIC without precision
[ https://issues.apache.org/jira/browse/OPENJPA-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314475#comment-17314475 ]
ASF subversion and git services commented on OPENJPA-2859:
----------------------------------------------------------
Commit 1c30090c8c611843860ff83be862e22cbcf46cee in openjpa's branch refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=1c30090 ]
OPENJPA-2859 use DOUBLE instead of NUMERIC
by default NUMERIC has no fraction digits, so rather use
DOUBLE data type which is a 64bit double value.
> [HSQLDB] HSQLDictionary wrongly maps double to NUMERIC without precision
> ------------------------------------------------------------------------
>
> Key: OPENJPA-2859
> URL: https://issues.apache.org/jira/browse/OPENJPA-2859
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 3.1.2
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Major
> Fix For: 3.1.3
>
>
> Right now we create a {{NUMERIC}} field without any precision digits for double fields. This results in zero decimal fractions, which is clearly wrong.
> We should rather use DOUBLE SQL type, which is a 64bit 'aprox' type. If someone wants to use a fixed prec+scale then use {{BigDecimal}} which will be mapped as {{DECIMAL(n,m)}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)