docs(intent): deleting an expansion's master removes the rows it generated - #203
Merged
Conversation
…rated The reference said what a span change does to the generated child set and nothing about what a delete does. Deleting the master left the rows behind - and because a foreign key is never a database constraint in Dirigible, nothing else would have stopped them, so they went on feeding roll-ups and reports for a record that no longer existed.
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.
Documents the delete half of
expansions, shipped in eclipse-dirigible/dirigible#6838 (issue eclipse-dirigible/dirigible#6821).The reference said what a span change does to the generated child set and nothing about what a delete does — and until #6838 nothing did: the rows outlived the record, still counted by every roll-up and report. Because a foreign key is never a database constraint in Dirigible (referential integrity is a business-layer check), nothing else would have stopped them either, so a reader could not infer the behaviour from anywhere else on the site.
Adds the rule to
/help/intent/dsl-reference#expansions, including why the removal goes per-row through the child's repository (each row's delete event fires, so roll-ups and guards downstream run as for a hand-deleted row).npx vitepress build docspasses.