Changes between Version 5 and Version 6 of ebXMLPersistenceLayer

Timestamp:

08/02/08 07:38:01 (16 years ago)

Author:

heikki

Comment:

--

ebXMLPersistenceLayer

@@ -32 +32 @@
 
 The fourth strategy is to represent inheritance relationships as relational foreign key associations. Every class/subclass that declares persistent properties—including abstract classes and even interfaces—has its own table. The primary advantage of this strategy is that the SQL schema is normalized. A polymorphic association to a particular subclass may be represented as a foreign key referencing the table of that particular subclass. This seems a preferred strategy but its performance may be detrimental for large class hierarchies as queries require a join across many tables.
+
+TODO conclusion?
+
+----
+
+=== Custom Types ===
+
+The following classes are represented as Custom Types in the Hibernate mapping:
+
+ * !InternationalString
+ * !VersionInfo
+
+TODO finish