@@ -1043,14 +1043,15 @@ finally
1043
1043
</itemizedlist >
1044
1044
1045
1045
<para >
1046
- Mapping an association (many-to-one, or collection) with <literal >cascade="all"</literal >
1046
+ Mapping an association (many-to-one, one-to-one or collection) with <literal >cascade="all"</literal >
1047
1047
marks the association as a <emphasis >parent/child</emphasis > style relationship where
1048
1048
save/update/deletion of the parent results in save/update/deletion of the child(ren).
1049
1049
Futhermore, a mere reference to a child from a persistent parent will result in save / update
1050
1050
of the child. The metaphor is incomplete, however. A child which becomes unreferenced by its
1051
- parent is <emphasis >not</emphasis > automatically deleted, except in the case of a
1052
- <literal >< one-to-many> </literal > association mapped with
1053
- <literal >cascade="all-delete-orphan"</literal >. The precise semantics of cascading operations
1051
+ parent is <emphasis >not</emphasis > automatically deleted, except in the cases of
1052
+ <literal >< one-to-many> </literal > and <literal >< one-to-one> </literal > associations
1053
+ that have been mapped with <literal >cascade="all-delete-orphan"</literal > or
1054
+ <literal >cascade="delete-orphan"</literal >. The precise semantics of cascading operations
1054
1055
are as follows:
1055
1056
</para >
1056
1057
@@ -1081,8 +1082,8 @@ finally
1081
1082
<para >
1082
1083
If a transient child is dereferenced by a persistent parent, <emphasis >nothing
1083
1084
special happens</emphasis > (the application should explicitly delete the child if
1084
- necessary) unless <literal >cascade="all-delete-orphan"</literal >, in which case the
1085
- "orphaned" child is deleted.
1085
+ necessary) unless <literal >cascade="all-delete-orphan"</literal > or
1086
+ < literal >cascade="delete-orphan"</ literal >, in which case the "orphaned" child is deleted.
1086
1087
</para >
1087
1088
</listitem >
1088
1089
</itemizedlist >
0 commit comments