openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <>
Subject [jira] Commented: (OPENJPA-213) @Column with precision and scale should result in NUMERIC(precision, scale)
Date Tue, 12 Feb 2008 03:15:08 GMT


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:
>             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.

View raw message