docs(glue): an expansion's rows do not outlive their master - #32
Open
delchev wants to merge 1 commit into
Open
Conversation
expansions describes the generated child set as owned by the expansion, but the page only said what a span CHANGE does. Deleting the master left the rows as the one part of the record that survives it - orphans still counted by every roll-up and report - and the page gave a reader no way to know that.
This was referenced Aug 19, 2026
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.
Adds the delete rule to the
expansionssection of/spec/glue.The construct already describes the generated child set as owned by the expansion, but the page only said what a span change does. Deleting the master left the rows behind — the one part of a record that survives it, still pointing at an id that no longer resolves and still counted by every roll-up, report and balance that counted them while the record existed.
Referential integrity is not the missing half: where it is enforced the delete is refused instead, which leaves an author with rows they never entered and no way to remove them — and which of the two outcomes an author meets is a property of the deployment rather than of the intent.
Paired with specification proposal IntentFile/intent-specification#41 (the normative text here is that proposal's
Specification textverbatim). Reference implementation: eclipse-dirigible/dirigible#6838.npx vitepress build docspasses.