site: the null case of a guard's key-tuple and of a posting's rule match - #56
Open
delchev wants to merge 1 commit into
Open
site: the null case of a guard's key-tuple and of a posting's rule match#56delchev wants to merge 1 commit into
delchev wants to merge 1 commit into
Conversation
Two lookups by value whose absent case the pages did not state. An aggregate already says a source row with any grouping key unset belongs to no tuple and is ignored; the guard section now says its half - such a record is not guarded at all. And a posting's rule match is a literal that has to say something: a blank one matches no rule row and sends every source document to the unposted worklist with nothing failing anywhere. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Site counterpart of spec proposal IntentFile/intent-specification#73 (implementation: eclipse-dirigible/dirigible#7253).
spec/entities(kind: guard): a record with any of the aggregate's grouping keys unset is not guarded at all - it belongs to no key-tuple, the aggregate itself ignores such a row, so it contributes to no total and can breach no minimum. The page already said the guard recomputes the total for the incoming record's key-tuple; it did not say what happens when there is no tuple.spec/glue(postings):rule.matchis a singlecolumn: literalselector and the literal has to say something - a blank one matches no rule row and sends every source document to the unposted worklist while everything stays healthy. A rule row whose match column is empty is a different thing and is called out as such.Built clean with
npx vitepress build docs.🤖 Generated with Claude Code