Skip to content

Prune tables beneath a skipped relation - #87

Merged
martinv13 merged 2 commits into
cre-dev:mainfrom
martinv13:fix/issue-83-skip-prunes-subtree
Oct 20, 2026
Merged

martinv13 merged 2 commits into
cre-dev:mainfrom
martinv13:fix/issue-83-skip-prunes-subtree

Conversation

@martinv13

Copy link
Copy Markdown
Collaborator

Closes #83.

Skipping a relation with transform: skip removed its table but not the tables beneath it. The child table was simplified before the skip was applied, which marked its own children as kept, so they were created and stayed empty.

The skip is now read from the field config and applied before the child table is simplified. Tables beneath a skipped relation are pruned unless another kept relation references them.

  • test_field_skip_relation also skips item.product and checks that producttype, intfeaturetype and stringfeaturetype are pruned (fails before the fix).
  • The example from the issue now only creates root.
  • docs/configuring.md states that tables beneath a skipped relation are pruned too.
  • No snapshot changes. Full suite on DuckDB: 249 passed, 76 skipped.

🤖 Generated with Claude Code

martinv13 and others added 2 commits October 20, 2026 23:05
A skipped relation's child table was simplified before the skip was
applied, which marked the tables beneath it as kept. They were created
and stayed empty. The skip is now applied before simplifying the child.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@martinv13
martinv13 merged commit 66b2ec6 into cre-dev:main Oct 20, 2026
10 checks passed
@martinv13
martinv13 deleted the fix/issue-83-skip-prunes-subtree branch October 20, 2026 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Skipping a field leaves empty tables for the types beneath it

1 participant