org.hibernate.engine
Class CascadeStyle.MultipleCascadeStyle
- CascadeStyle
- Serializable
public static final class CascadeStyle.MultipleCascadeStyle
ALL , ALL_DELETE_ORPHAN , DELETE , DELETE_ORPHAN , EVICT , LOCK , MERGE , NONE , PERSIST , REFRESH , REPLICATE , UPDATE |
MultipleCascadeStyle
public MultipleCascadeStyle(CascadeStyle[] styles)
doCascade
public boolean doCascade(CascadingAction action)
For this style, should the given action be cascaded?
- doCascade in interface CascadeStyle
action
- The action to be checked for cascade-ability.
- True if the action should be cascaded under this style; false otherwise.
hasOrphanDelete
public boolean hasOrphanDelete()
Do we need to delete orphaned collection elements?
- hasOrphanDelete in interface CascadeStyle
- True if this style need to account for orphan delete
operations; false othwerwise.
reallyDoCascade
public boolean reallyDoCascade(CascadingAction action)
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(CascadingAction)
; for certain
styles (currently only delete-orphan), however, we need to be able to
control this seperately.
- reallyDoCascade in interface CascadeStyle
action
- The action to be checked for cascade-ability.
- True if the action should be really cascaded under this style;
false otherwise.
toString
public String toString()