You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Michael Bouschen (JIRA)" <ji...@apache.org> on 2011/02/04 17:54:12 UTC

[jira] Updated: (JDO-674) 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)

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

Michael Bouschen updated JDO-674:
---------------------------------

    Affects Version/s: JDO 3
        Fix Version/s: JDO 3 maintenance release 1

> 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
>            Reporter: Andy Jefferson
>             Fix For: JDO 3 maintenance release 1
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira