proposal: A row outside every tuple is not guarded, and a rule match is a literal that says something - #73
Open
delchev wants to merge 1 commit into
Open
proposal: A row outside every tuple is not guarded, and a rule match is a literal that says something#73delchev wants to merge 1 commit into
delchev wants to merge 1 commit into
Conversation
…is a literal that says something Two lookups by value whose null case the specification does not state. An aggregate is normative that a source row with any grouping key unset belongs to no tuple and is ignored; the guard that recomputes the same total says nothing about such a row, so it is weighed either against zero or against a pool of rows the aggregate ignores - two readings that disagree on whether a write is accepted. A posting's rule match is called a literal, but not required to be one that says something: an empty value looks up the empty rule row, matches nothing, and skips every source document to the unposted worklist with the model, the generation and the deployment all healthy. 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.
Two lookups by value whose absent case the specification does not state. Filed as one proposal because they are one class of gap and one implementation issue (eclipse-dirigible/dirigible#7180).
A guard over an aggregate.
aggregatesis normative that a source row with any grouping key unset belongs to no tuple and MUST be ignored.checks: kind: guardrecomputes the same total for the incoming row's key-tuple, and is normative about the recompute, but says nothing about a row that has no tuple - so such a record is weighed either against zero or against a pool of rows the aggregate itself ignores, two readings that disagree on whether a write is accepted. The proposal states the guard's half: a record belonging to no tuple is not guarded at all.A posting's determination rule.
rule.match's value is called a literal but is not required to be one that says anything. An empty one is a lookup for the empty value: it matches no rule row, so the posting takes its documented "no rule row" path for every source document, with the model well-formed, the generation successful and the deployment healthy. The proposal makes an absent or blank match value an authoring error.No new keys in either case.
🤖 Generated with Claude Code