[ http://issues.apache.org/jira/browse/JDO-167?page=all ]
Michael Watzek updated JDO-167:
-------------------------------
Attachment: JDO-167.patch
The attached patch fixes this issue.
> Inheritance mapping 2 needs to be changed to support polymorphic
> relationships to Employees
> -------------------------------------------------------------------------------------------
>
> Key: JDO-167
> URL: http://issues.apache.org/jira/browse/JDO-167
> Project: JDO
> Type: Bug
> Components: tck20
> Reporter: Michael Watzek
> Assignee: Michael Watzek
> Attachments: JDO-167.patch
>
> Inheritance mapping 2 is incomplete wrt Employee relationships. Due to this
> lack, implementations cannot figure out the right runtime type at navigation
> time, e.g. navigating from Project to Employee.
> In t-conference, Sep 30, Craig proposed to drop the identity propties from PK
> columns of tables persons, fulltimeemployees, parttimeemployees. Instead, we
> introduce implementation-defined sequences to generate unique key values for
> all instances of the Person class hierarchy. Having unique PK values for each
> row in the hierarchy, implementations are able to find out the right runtime
> type when navigating Employee relationships.
> We need to adapt the schema and the ORM metadata in order to reflect these
> changes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
