Initializes a new instance of the CascadingAction class

Cascade the action to the child object.

Determines whether the specified Object is equal to the current Object.

Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.

Given a collection, get an iterator of the children upon which the current cascading action should be visited.

Serves as a hash function for a particular type.

Iterate just the elements of the collection that are already there. Don't load any new elements from the database.

Gets the Type of the current instance.

Creates a shallow copy of the current Object.

Called (in the case of RequiresNoCascadeChecking returning true) to validate that no cascade on the given property is considered a valid semantic.

Returns a string that represents the current object.

Apply a "between" constraint to the named property Note: throws an exception outside of a QueryOver expression

Apply an "in" constraint to the named property Note: throws an exception outside of a QueryOver expression

Apply an "in" constraint to the named property Note: throws an exception outside of a QueryOver expression

Execute persist during flush time

Does this action potentially extrapolate to orphan deletes?

Should this action be performed (or noCascade consulted) in the case of lazy properties.

Does the specified cascading action require verification of no cascade validity?