[
https://issues.apache.org/jira/browse/OPENJPA-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475004#comment-13475004
]
Rick Curtis commented on OPENJPA-213:
-------------------------------------
Per one of my last comment messages in OPENJPA-1224 :
Rick Curtis submitted changeset 822288 to trunk in openjpa (3 files) -
06/Oct/09 15:14
OPENJPA-1224: backing out changes while investigating a test regression.
It looks like this change regressed some of our internal tests and I backed the
change out. I'd suggest posting a question to the users mailing list with
details on what you are hitting as opposed to posting comments to a JIRA that
was closed over 4 years ago.
Thanks,
Rick
> @Column with precision and scale should result in NUMERIC(precision, scale)
> ---------------------------------------------------------------------------
>
> Key: OPENJPA-213
> URL: https://issues.apache.org/jira/browse/OPENJPA-213
> Project: OpenJPA
> Issue Type: Improvement
> Components: jpa
> Affects Versions: 0.9.7, 1.1.0
> Reporter: Jacek Laskowski
> Assignee: Michael Dick
> Fix For: 1.3.0, 2.0.0-M2
>
> Attachments: OPENJPA-213.patch.txt
>
>
> @Column provides the precision and scale attributes, but there's no (easy)
> way to figure out how it affects the way OpenJPA works if any. It looks like
> OpenJPA reads the type of a persistent field and when it's double it maps it
> to DOUBLE in Derby regardless of the other attributes. When precision and
> scale are specified, a DDL should use NUMERIC(precision, scale) or its
> synonim - DECIMAL(precision, scale).
--
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: http://www.atlassian.com/software/jira
