Fix to support composite key columns (GroupByColumns) in StatExtractor #159
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.
This update resolves an issue in StatExtractor where an error occurred during the extraction of relationship statistics when one of the columns in the relationship was part of a composite key (GroupByColumns). The error message was: "Column [] is part of composite key, but not all columns of the composite key are included in the expression or its dependent expression." This fix applies only to models with a compatibility level of 1200 or higher, as GroupByColumns is not available in levels 1100 and 1103.