openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Sandor (JIRA)" <>
Subject [jira] Commented: (OPENJPA-213) @Column with precision and scale should result in NUMERIC(precision, scale)
Date Mon, 19 May 2008 11:39:58 GMT


Thomas Sandor commented on OPENJPA-213:

I'm using openjpa-1.1.0-r422266:656510 on DB2 and SQLSERVER for testing.
Unfortunately mappingtool still creates DOUBLE column on DB2 and FLOAT(32) on SQLSERVER for
BigDecimal columns with precisions.
Is there any patch or progress in this issue?

> @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