openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <>
Subject [jira] [Commented] (OPENJPA-2280) MappingTool ignores column precision / scale for some databases
Date Mon, 04 Feb 2013 19:18:13 GMT


Kevin Sutter commented on OPENJPA-2280:

1)  In general, I agree with this.  What are the default values for precision and scale when
they are not set via @Column annotation?  One value, both values, or neither value.
2)  I think I agree with this.  Need to clarify what you mean by "same scale".  Same scale
as the input value, or same scale as the field definition (metadata)?
3)  I think the storeLargeNumberAsString property is orthogonal to this discussion.  Granted,
it's another means of storing a BigDecimal, but let's fix BigDecimal first and then worry
about how this storeLargeNumberAsString property might be affected.

Another pertinent question is what will the affect be to existing applications if the numericTypeName
is changed from Double to Decimal for Derby and DB2?  We will have to support Double (to the
extent possible) for existing applications that have their schemas defined with this data
type.  Maybe some type of warning message will need to be displayed if the Double type is

Thanks for looking into this, Pinaki.
> MappingTool ignores column precision / scale for some databases
> ---------------------------------------------------------------
>                 Key: OPENJPA-2280
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 1.2.3, 2.3.0, 2.2.1
>            Reporter: Rick Curtis
> This JIRA is the same issue as reported by OPENJPA-1224.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message