Package org.hibernate.persister.entity.mutation
Defines support for performing mutation operations originating
from persistence-context events.
-
Interface Summary Interface Description AttributeAnalysis Results of analyzing an attribute in terms of handling update operationsDeleteCoordinator Coordinates the deleting of an entity.EntityMutationTarget Anything that can be the target of mutationsEntityTableMapping.KeyValueConsumer InsertCoordinator Coordinates the inserting of an entity.MutationCoordinator Coordinates the mutation operations of an entity.UpdateCoordinator Coordinates the updating of an entity.UpdateCoordinatorStandard.DirtinessChecker UpdateCoordinatorStandard.InclusionChecker UpdateValuesAnalysis Contains an aggregated analysis of the values for an update mutation to determine behavior such as skipping tables which contained no changes, etc. -
Class Summary Class Description AbstractDeleteCoordinator Template support for DeleteCoordinator implementations.AbstractMutationCoordinator Base support for coordinating mutations against an entityDeleteCoordinatorSoft DeleteCoordinator for soft-deletesDeleteCoordinatorStandard Coordinates standard deleting of an entity.EntityTableMapping Descriptor for the mapping of a table relative to an entityEntityTableMapping.KeyColumn EntityTableMapping.KeyMapping InsertCoordinatorStandard Coordinates the insertion of an entity.InsertCoordinatorStandard.InsertValuesAnalysis MergeCoordinator SpecializedUpdateCoordinatorformerge into.TableSet Represents a Set of TableMapping(s); table mappings are identified by an ordered unique id: the order in which they are updated within the scope of a particular persister.UpdateCoordinatorNoOp UpdateCoordinatorStandard Coordinates the updating of an entity. -
Enum Summary Enum Description AttributeAnalysis.DirtynessStatus Dirty-ness status of each attribute: it's useful to differentiate when it's definitely dirty, when it's definitely not dirty, and when we need to treat it like dirty but there is no certainty - for example because we didn't actually load the value from the database.