CascadeFetch follows the Composite aggregation marked associations and make sure that things are loaded.

If your viewmodel shall delete an object that has a lot of composite aggregations it can be smart to first do CascadeFetch as an ocl column as this will be managed by the Queryplanner and fetched in as few roundtrips as possible, instead of cold running delete in an action that will lazy load things , often one by one.

CascadeFetch returns an integer of how many objects that are included in the aggregate.