API Note
The names used here are logical. E.g. "inserting a row" may actually
execute an UPDATE statement instead of an INSERT. This is generally
delineated based on whether there is a collection table involved or
not. In terms of our usual model, this breaks down to the distinction
between org.
and org..
| Modifier and Type | Interface and Description |
|---|---|
| public interface | |
| public interface | CollectionOperationCoordinator
Base contract for coordination of collection mutation operations |
| public interface | DeleteRowsCoordinator
Coordinates the deletion of entries removed from the collection -
|
| public interface | InsertRowsCoordinator
Coordinates the logical insertion of collection entries which are not yet persistent. |
| public interface | OperationProducer
Callback for producing a |
| public interface | RemoveCoordinator
Removes the collection:
|
| public interface |
| Modifier and Type | Class and Description |
|---|---|
| public abstract class | |
| public class | |
| public class | DeleteRowsCoordinatorNoOp
DeleteRowsCoordinator implementation for cases where deletion is not enabled |
| public class | |
| public class | DeleteRowsCoordinatorTablePerSubclass
OneToMany delete coordinator if the element is a |
| public class | |
| public class | |
| public class | InsertRowsCoordinatorTablePerSubclass
OneToMany insert coordinator if the element is a |
| public class | |
| public class | RemoveCoordinatorStandard
Handles complete removal of a collection by its key |
| public class | RemoveCoordinatorTablePerSubclass
OneToMany remove coordinator if the element is a |
| public class | RowMutationOperations
Composition of the |
| public class | |
| public class | |
| public class | UpdateRowsCoordinatorStandard
UpdateRowsCoordinator implementation for cases with a separate collection table |
| public class | UpdateRowsCoordinatorTablePerSubclass
OneToMany update coordinator if the element is a |