openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-213) @Column with precision and scale should result in NUMERIC(precision, scale)
Date Tue, 20 May 2008 10:52:55 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Dick updated OPENJPA-213:
---------------------------------

    Attachment: OPENJPA-213.patch.txt

Attaching a patch. The patch only addresses the "first" part of the fix ie BigDecimal will
now be mapped to NUMERIC instead of DOUBLE.

The second part of the fix is to promote a field of type Double to NUMERIC if scale or precision
 is specified on the annotation. 

> @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
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message