diff --git a/reference/en/modules/inheritance_mapping.xml b/reference/en/modules/inheritance_mapping.xml
index 32b643d8f0..a62133d521 100644
--- a/reference/en/modules/inheritance_mapping.xml
+++ b/reference/en/modules/inheritance_mapping.xml
@@ -243,41 +243,10 @@
Limitations
- TODO: This section needs to be rewritten, Hibernate3 has almost no limitations on inheritance mappings
-
-
-
- Hibernate assumes that an association maps to exactly one foreign key column.
- Multiple associations per foreign key are tolerated (you might need to specify
- inverse="true" or insert="false" update="false"),
- but there is no way to map any association to multiple foreign keys. This means that:
-
-
-
-
-
- when an association is modified, it is always the same foreign key that is
- updated
-
-
-
-
- when an association is fetched lazily, a single database query is used
-
-
-
-
- when an association is fetched eagerly, it may be fetched using a single
- outer join
-
-
-
-
-
- In particular, it implies that polymorphic one-to-many associations to
- classes mapped using the table-per-concrete-class strategy are
- not supported. (Fetching this association would
- require multiple queries or multiple joins.)
+ There are certain limitations to the "implicit polymorphism" approach to
+ the table-per-concrete-class mapping strategy. There are somewhat less
+ restrictive limitations to <union-subclass>
+ mappings. (TODO)
@@ -343,6 +312,17 @@
not supported
not supported
+
+ table-per-concrete-class (union-subclass)
+ ??
+ ??
+ <one-to-many> (inverse="true" only)
+ ??
+ s.get(Payment.class, id)
+ from Payment p
+ from Order o join o.payment p
+ supported
+