[
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17343642#comment-17343642
]
Craig L Russell commented on JDO-709:
-------------------------------------
If a field is annotated with a Column annotation, it is assumed to be
persistent.
I believe that if a field is annotated with a Convert annotation it should be
assumed to be persistent, since the only possible reason for the Convert
annotation is to map values to and from the database. This should be true even
if there is no Column annotation because the defaults in the Column annotation
might be sufficient for the converted field.
>From the proposed Chapter 18 changes:
> For fields using converters, the default jdbc-type is the default jdbc-type
> for the database type of the AttributeConverter for the field.
> Standardize field/property converters
> -------------------------------------
>
> Key: JDO-709
> URL: https://issues.apache.org/jira/browse/JDO-709
> Project: JDO
> Issue Type: New Feature
> Components: api, specification, tck
> Reporter: Matthew T. Adams
> Assignee: Craig L Russell
> Priority: Minor
> Labels: converstion, converter, jdo, type, type-converter
> Fix For: JDO 3.2
>
> Attachments: JDO-709-01.patch, JDO-709-3.patch, JDO-709-4.patch
>
>
> This request is to standardize a user's ability to specify conversions of
> fields or properties of persistence-capable classes. Currently, this is left
> to vendor extensions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
