[
https://issues.apache.org/jira/browse/OPENJPA-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567936#action_12567936
]
Craig Russell commented on OPENJPA-213:
---------------------------------------
In general, an annotation on a persistent field should override the type of the
field, and orm metadata should override the annotation.
So I agree with the plaintiff that if OpenJPA generates columns, the annotation
should be consulted to establish the column metadata in the database.
Absent any annotation or orm metadata, I agree that the jdbc mapping is
reasonable. But if the user specifies a mapping, I believe it should override
the jdbc defaults.
> @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
> Reporter: Jacek Laskowski
> Assignee: Michael Dick
>
> @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.
-
You can reply to this email to add a comment to the issue online.
