Rename misleading Total Executions label in drill-down summaries (fixes #194)#205
Merged
erikdarlingdata merged 1 commit intodevfrom Feb 20, 2026
Merged
Rename misleading Total Executions label in drill-down summaries (fixes #194)#205erikdarlingdata merged 1 commit intodevfrom
erikdarlingdata merged 1 commit intodevfrom
Conversation
…ixes #194) Plan cache execution_count is a cumulative counter — MAX is the correct aggregation, matching the main grid. The "Total Executions" label implied a sum, confusing users. Renamed to "Executions" in QueryStatsHistory and ProcedureHistory windows. Query Store window keeps "Total Executions" since it correctly sums interval deltas. Co-Authored-By: Claude Opus 4.6 <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.
Summary
execution_countis a cumulative counter (total since plan was cached), so MAX is the correct aggregation — matching the main gridTest plan
🤖 Generated with Claude Code