[
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335829#comment-17335829
]
Craig L Russell commented on JDO-709:
-------------------------------------
Great test case.
For me, two questions remain:
1. should we allow fields of converted types to be used as primary keys,
indexes, or optimistic concurrency fields?
I can see a use for indexes but perhaps not other cases. Converting a database
value that is indexed seems to be useful.
Converting database primary keys has no barriers to understanding but might
pose some implementation challenges. But absent a compelling use case I can
understand why we might disallow it.
2. Do we need a test case for using annotation to define the converter, or are
we happy with using external metadata?
If we want to test annotation, that would imply another class, e.g.
PCRectStringAnnotated. Same test methods but using PCRectStringAnnotated
instead of PCRectString...
> 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)
