You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This proposes a new representation of aggregate plans that gets rid of the first grouping Value in the underlying select expression.
Doing so would achieve two goals:
Avoid ambiguous derivation of fields: currently, a grouping field exists twice, once in the grouping value RCV, and another time in the quantifier of the originating table. This is unnecessary and makes integration of the value mapping API more complex.
Overall simplification in the plan generation logic: maintaining the grouping Value is complex and requires some state that increases the complexity of the plan generator. Getting rid of the grouping Value would help streamlining the logic of the plan generator.
The text was updated successfully, but these errors were encountered:
This proposes a new representation of aggregate plans that gets rid of the first grouping Value in the underlying select expression, and consumes @normen662's fix for an issue with Value simplification engine not being to handle QOV correctly when pulling up a Value.
It addresses #2763 .
This proposes a new representation of aggregate plans that gets rid of the first grouping
Value
in the underlyingselect
expression.Doing so would achieve two goals:
Value
is complex and requires some state that increases the complexity of the plan generator. Getting rid of the groupingValue
would help streamlining the logic of the plan generator.The text was updated successfully, but these errors were encountered: