Assign updated bitemporal times to the receiver after update/destroy #118
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.
See also #117
Closes #100
We originally planned to assign all attributes to the receiver after update/destroy, but ran into some issues. See #117 for the motivation of this PR.
This PR changes the update/delete operation to only assign valid time/transaction time instead of all attributes. This eliminates the inconsistency described in #117, but the receiver does not always match the actual history when a callback is applied.
Below is an example:
All attribute assignments were required to prevent this issue.
Since we don't assign all attributes, the only reliable receiver attributes are the following. Do not trust that any other value is equal to the latest history.
swapped_id
swapped_id_previously_was
valid_from
valid_to
transaction_from
transaction_to
saved_changes