Changes between Version 5 and Version 6 of ebXMLPersistenceLayer


Ignore:
Timestamp:
Aug 2, 2008, 7:38:01 AM (16 years ago)
Author:
heikki
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ebXMLPersistenceLayer

    v5 v6  
    3232
    3333The 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.
     34
     35TODO conclusion?
     36
     37----
     38
     39=== Custom Types ===
     40
     41The following classes are represented as Custom Types in the Hibernate mapping:
     42
     43 * !InternationalString
     44 * !VersionInfo
     45
     46TODO finish