|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
09/Dec/05 12:37 AM
|
|
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.
|
|
Description
|
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.
|
Show » |
made changes - 08/Dec/05 12:23 AM
| Field |
Original Value |
New Value |
|
Attachment
|
|
JDO-167.patch
[ 12321201
]
|
made changes - 08/Dec/05 07:54 PM
|
Attachment
|
|
JDO-167.patch2
[ 12321225
]
|
made changes - 09/Dec/05 12:37 AM
|
Resolution
|
|
Fixed
[ 1
]
|
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
|
Bug
Resolved
Major
Inheritance mapping 2 needs to be changed to support polymorphic relationships to Employees
