Ability to save entities without triggering events#5343
Open
knstvk wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds two
SaveContexthints that let callers suppress lifecycle events when saving viaDataManager, for use cases like bulk import and technical/system updates that shouldn't trigger business logic.New hints (
io.jmix.data.PersistenceHints):SKIP_ENTITY_SAVING_EVENT— suppressesEntitySavingEventSKIP_ENTITY_CHANGED_EVENT— suppressesEntityChangedEventThe two are independent; default behavior (hints absent) is unchanged.
Implementation:
JpaDataStore.saveAll()skipsEntitySavingEventpublishing;beforeSaveTransactionCommit()skipsEntityChangedEventpublishing while still running change collection and entity detachment.Caveats (documented on the constants): suppressing
EntitySavingEventalso skips multitenancy tenant-id assignment; suppressingEntityChangedEventalso skips full-text search re-indexing and security cache invalidation. Audit fields (JPA descriptor level) and the audit entity log (JpaLifecycleListener) are not affected.