-
Notifications
You must be signed in to change notification settings - Fork 1
Include unmapped targets with most queries #27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
rustybee42
wants to merge
1
commit into
main
Choose a base branch
from
rb/unmapped-targets
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+23
−11
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| DROP VIEW targets_ext; | ||
|
|
||
| CREATE VIEW targets_ext AS | ||
| SELECT e.alias, t.*, n.node_uid | ||
| FROM targets AS t | ||
| INNER JOIN entities AS e ON e.uid = t.target_uid | ||
| LEFT JOIN nodes AS n USING(node_type, node_id) | ||
| ; |
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion(blocking): it is unfortunate a DB migration is required for this change. So we can at least eliminate the upgrade pain for users (most who are unaffected by this particular change), what do you think about automatically applying minor DB schema updates when needed?
We could introduce a new option for this (e.g.,
--upgrade=auto) so it is opt in. This would be particularly helpful for environments that use tools like Ansible for automated deployments/upgrades to avoid requiring post-upgrade steps for specific minor releases.Blocking not because we need to introduce any automatic migration in this PR, but because I want to discuss how we want to generally handle database upgrades in minor releases before we merge our first DB schema update.