Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 258691

Summary: Table Per Class inheritance support
Product: [WebTools] Dali JPA Tools Reporter: Karen Butzke <karenfbutzke>
Component: GeneralAssignee: Karen Butzke <karenfbutzke>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3 CC: neil.hauge
Version: 2.1Keywords: plan
Target Milestone: 2.2 M6   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on:    
Bug Blocks: 243477    

Description Karen Butzke CLA 2008-12-12 14:28:04 EST 
Currently we allow you to choose the TABLE_PER_CLASS inheritance strategy, but beyond that we do not really support it.  We need to investigate the validation errors needed for this, as well as how the default in the entity hierarchy need to be changed in this case.  There might be other things beyond this, but just wanted to get a bug entered.

EclipseLink will support this with bug 249860
Comment 1 Karen Butzke CLA 2009-01-05 12:37:22 EST 
No default table on abstract entities with TABLE_PER_CLASS inheritance.  Some thoughts on how to support this include displaying '<None>' in the Table combo box instead of 'Default ()'.  Also possibly displaying a lightbulb icon on the table combo where there is hover help stating that no table should be defined for abstract entities that are part of a table per class inheritance hierarchy.

 We also need to support attribute overrides for subclasses of abstract entities with TABLE_PER_CLASS inheritance.

No discriminator column and no discriminator values apply, display '<None>' in the widgets instead of 'Default'.  Could do the same lightbulb icon for these widgets as well, to help show the user that they are not supported in this case.  Would also need validation for these cases in case the user does define them.

Same hover help lightbulb icon for pkJoinColumns when the inheritance is not Joined and on the root of the hierarchy.
Comment 2 Karen Butzke CLA 2009-01-07 11:35:13 EST 
see EclipseLink bug 259829, they have the same problem
Comment 3 Karen Butzke CLA 2009-03-05 12:14:25 EST 
This has been fixed.  Table-per-class inheritance support was added to the core model.  EclipseLink 1.0 platform has a validation error if table-per-class inheritance is used.  Generic platform has a validation warning stating that table-per-class is not portable and might not be supported by the provider.