Package org.hibernate.engine.spi
Class CascadeStyles.BaseCascadeStyle
java.lang.Object
org.hibernate.engine.spi.CascadeStyles.BaseCascadeStyle
- All Implemented Interfaces:
Serializable
,CascadeStyle
- Direct Known Subclasses:
CascadeStyles.MultipleCascadeStyle
- Enclosing class:
- CascadeStyles
- See Also:
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionboolean
Do we need to delete orphaned collection elements?boolean
reallyDoCascade
(CascadingAction<?> action) Probably more aptly named something like doCascadeToCollectionElements(); it is however used from both the collection and to-one logic branches...Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
Methods inherited from interface org.hibernate.engine.spi.CascadeStyle
doCascade
-
Constructor Details
-
BaseCascadeStyle
public BaseCascadeStyle()
-
-
Method Details
-
reallyDoCascade
Description copied from interface:CascadeStyle
Probably more aptly named something like doCascadeToCollectionElements(); it is however used from both the collection and to-one logic branches...For this style, should the given action really be cascaded? The default implementation is simply to return
CascadeStyle.doCascade(org.hibernate.engine.spi.CascadingAction<?>)
; for certain styles (currently only delete-orphan), however, we need to be able to control this separately.- Specified by:
reallyDoCascade
in interfaceCascadeStyle
- Parameters:
action
- The action to be checked for cascade-ability.- Returns:
- True if the action should be really cascaded under this style; false otherwise.
-
hasOrphanDelete
public boolean hasOrphanDelete()Description copied from interface:CascadeStyle
Do we need to delete orphaned collection elements?- Specified by:
hasOrphanDelete
in interfaceCascadeStyle
- Returns:
- True if this style need to account for orphan delete operations; false otherwise.
-