proposal: an amended source rewrites its posting - #65
Merged
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
1 participant
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.
A source document does not reach a posting's moment only once: the amend path (issue, reject, correct, issue again) reaches it twice, and the post made the first time no longer describes the document. Today's idempotence answers "have I handled this source?" and leaves the stale post in place — a ledger that silently disagrees with the document it references.
The proposal states the behaviour without a new key: compare the derived content with the existing post, rewrite it when it differs, and stop at the created document's own status lifecycle, past which the divergence is reported and left to a reversing entry.
Implemented in eclipse-dirigible/dirigible#7086 (issue eclipse-dirigible/dirigible#7071).