Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Talk:EclipseLink/Development/JPA 1.0/table per class
Revision as of 14:51, 8 December 2008 by Unnamed Poltroon (Talk) (New page: ==Isn't this just Interface descriptors?== * This seems to be just interface descriptors, the requirements seem to be identical, it matter little whether the classes have an interface or a...)
Isn't this just Interface descriptors?
- This seems to be just interface descriptors, the requirements seem to be identical,
it matter little whether the classes have an interface or abstract class in common. Is would seem odd to have two pieces of identical duplicate code. Perhaps subclass TablePerClassInheritancePolicy from InterfacePolicy not InheritancePolicy.
- Why not just use the existing interface support, just add an interface descriptor for the abstract class (and process it as a MappedSuperclass)?
- We currently only support VariableOneToOne with interfaces, 1-1, 1-m, m-m are in theory possible just by setting the reference class, but most likely will not work as it is probably a lot more complex than just querying (deletes, mapping fields, pk uniqueness, type fields, constraints, ddl).
- What will occurs for Update-All, Delete-All query?
- Will joins be supported? Join fetch? Batch reading?
- Will we use an SQL UNION?
- Not sure I understand the bit on preparing and cloning selectionQueries?
- James.sutherland.oracle.com 18:51, 8 December 2008 (UTC)