| java.lang.Object | |
| ↳ | org.hibernate.engine.CascadeStyle |
 Known Direct Subclasses
|
Class Overview
A contract for defining the aspects of cascading various persistence actions.
See Also
Summary
| Nested Classes | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| CascadeStyle.MultipleCascadeStyle | |||||||||||
| Fields | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| ALL | save / delete / update / evict / lock / replicate / merge / persist | ||||||||||
| ALL_DELETE_ORPHAN | save / delete / update / evict / lock / replicate / merge / persist + delete orphans | ||||||||||
| DELETE | delete | ||||||||||
| DELETE_ORPHAN | delete + delete orphans | ||||||||||
| EVICT | evict | ||||||||||
| LOCK | lock | ||||||||||
| MERGE | merge | ||||||||||
| NONE | no cascades | ||||||||||
| PERSIST | create | ||||||||||
| REFRESH | refresh | ||||||||||
| REPLICATE | replicate | ||||||||||
| UPDATE | save / update | ||||||||||
| Public Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
For this style, should the given action be cascaded?
| |||||||||||
Factory method for obtaining named cascade styles
| |||||||||||
Do we need to delete orphaned collection elements?
| |||||||||||
Probably more aptly named something like doCascadeToCollectionElements(); it is
however used from both the collection and to-one logic branches...
| |||||||||||
|
[Expand]
Inherited Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
From class
java.lang.Object
| |||||||||||
Fields
public static final CascadeStyle ALL
save / delete / update / evict / lock / replicate / merge / persist
public static final CascadeStyle ALL_DELETE_ORPHAN
save / delete / update / evict / lock / replicate / merge / persist + delete orphans
Public Methods
public abstract boolean doCascade (CascadingAction action)
For this style, should the given action be cascaded?
Parameters
| action | The action to be checked for cascade-ability. |
|---|
Returns
- True if the action should be cascaded under this style; false otherwise.
public static CascadeStyle getCascadeStyle (String cascade)
Factory method for obtaining named cascade styles
Parameters
| cascade | The named cascade style name. |
|---|
Returns
- The appropriate CascadeStyle
public boolean hasOrphanDelete ()
Do we need to delete orphaned collection elements?
Returns
- True if this style need to account for orphan delete operations; false othwerwise.
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 returndoCascade(CascadingAction); for certain
styles (currently only delete-orphan), however, we need to be able to
control this seperately.Parameters
| action | The action to be checked for cascade-ability. |
|---|
Returns
- True if the action should be really cascaded under this style; false otherwise.