Changes between Version 4 and Version 5 of ebXMLPersistenceLayer

Timestamp:

Aug 2, 2008, 7:17:55 AM (16 years ago)

Author:

heikki

Comment:

--

ebXMLPersistenceLayer

@@ -25 +25 @@
  * Table per subclass
 
-The first strategy creates a different table for each subclass, and those tables all contain (repeat) the data from the common base class. The Hibernate mapping is unaware of the inheritance relation. The base class definition is thus denormalized. It is impossible to define polymorphic associations and problematic to define polymorphic queries.
+The first strategy creates a different table for each subclass, and those tables all contain (repeat) the properties from the common base class. The Hibernate mapping is unaware of the inheritance relation. The base class definition is thus denormalized. It is impossible to define polymorphic associations and problematic to define polymorphic queries.
 
 The second strategy also employs different tables for each subclass (thus base class columns are denormalized), but now the Hibernate mapping is made aware of the inheritance relation. This allows for polymorphic associations and avoids repeating the base class mapping multiple times in the Hibernate mapping.