Skip to content

docs(intent): deleting an expansion's master removes the rows it generated #203

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
delchev merged 1 commit into from
Aug 19, 2026
Merged

docs(intent): deleting an expansion's master removes the rows it generated #203

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion docs/help/intent/dsl-reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1301,7 +1301,12 @@ expansions:
```

A span change replaces the generated child set; never mix hand-entered rows into an expanded
child.
child. Deleting the master deletes the rows it generated: the expansion owns that set, and a
foreign key is never a database constraint in Dirigible (referential integrity is checked in the
generated repository), so nothing else would stop the rows from outliving the record they belong to
and going on feeding roll-ups and reports. The rows are removed one by one through the child's
repository, so each row's delete event still fires and the roll-ups and guards downstream of it run
exactly as they would for a hand-deleted row.

## rollups - denormalised parent totals

Expand Down