story(ccls-2289) cleardown opa assessment log #18
Conversation
This file contains 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.
When abandoning an application in the ProviderUI, the related Assessments (OPA_SESSION) and related rows from XXCCMS_OPA_ASSESSMENT_LOG are also deleted.
This table is only written to in the Connector, via the procedure OPA_AUDIT_LOG.CREATE_LOG.
If this cleardown is still needed, then this should be added to the CAAB. If deleting an Assessment should always lead to a truncation of assessment log data, then a relationship can be added between OpaSession and a new Entity OpaAssessmentLog to cascade the delete.