fix(insights): queries module system selector should match table#106443
Merged
DominikB2014 merged 1 commit intomasterfrom Jan 16, 2026
Conversation
github-actions
bot
added
the
Scope: Frontend
narsaynorath
approved these changes
Jan 16, 2026
DominikB2014
deleted the
dominikbuszowiecki/exp-644-system-none-always-on-backend-queries-query-summary-page
branch
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
The underlying query that is used to find possible db systems should match the the underlying query that is used to get the main data on the page. This is so there isn't a discrepancy between the possible db selector options and the rest of the data on the page (for example, you never have results in the table, but missing db selector options for those results)
fixes #104512