[
https://issues.apache.org/jira/browse/JDO-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474858#comment-13474858
]
Craig L Russell commented on JDO-674:
-------------------------------------
Chapter 15 has been updated:
15.6 ...
Another pattern maps all fields including superclass fields to columns in the
mapped table. This pattern is achieved by specifying complete-table for the
strategy.
Chapter 18 has been updated:
18.8 ...
The value "complete-table" means that this class has its own table. All of its
fields including superclass fields are mapped to columns in the mapped table.
19.1.24 has been updated to include the enum COMPLETE_TABLE.
> Support a way of defining inheritance strategy that results in a table per
> class with the table containing columns for all fields in the class (inc
> superclasses)
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JDO-674
> URL: https://issues.apache.org/jira/browse/JDO-674
> Project: JDO
> Issue Type: New Feature
> Components: api, specification, tck
> Affects Versions: JDO 3 (3.0)
> Reporter: Andy Jefferson
> Assignee: Craig L Russell
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: JDO-674.patch
>
>
> JPA provides an inheritance strategy "TABLE PER CLASS". In JPA this is
> defined in the root of an inheritance tree and implies that all classes in
> the inheritance tree have their own table that contains columns for all
> fields (inc fields in superclasses). There is currently no way to achieve
> this with JDO's strategy specification capability.
> Propose we provide one of the following
> 1. Just have a strategy "complete-table" specified in the root of the
> inheritance hierarchy that implies the same as the JPA situation. This is the
> simplest to define.
> 2. Have a strategy "complete-table" that can be specified on any class with
> the result that this class has a table containing columns for all fields (inc
> superclasses). There are difficulties in defining what happens in the case of
> a subclass - can it take any of the standard inheritance strategy settings ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
