db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (JIRA)" <j...@apache.org>
Subject [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)
Date Mon, 21 Feb 2011 10:55:38 GMT

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

Andy Jefferson updated JDO-674:
-------------------------------

    Attachment: JDO-674.patch

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

        

Mime
View raw message