You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Mark Struberg (Jira)" <ji...@apache.org> on 2021/04/04 11:52:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Mark Struberg updated OPENJPA-2859:
-----------------------------------
Summary: [HSQLDB] HSQLDictionary wrongly maps double to NUMERIC without precision (was: [HSQLDB] HSQLDictionary wrongly maps double to NUMBER without precision)
> [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)