Refresh catalog on ddl query execution#311
Merged
Merged
Conversation
…ver the catalog loading fails
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
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.
Refresh catalog on DDL query execution
Summary
This PR automatically refreshes the database catalog (sidebar tree) whenever the user executes a DDL query (e.g.,
CREATE,DROP,ALTER,TRUNCATE,RENAME). Previously, the sidebar would remain stale after schema changes, requiring the user to restart the application to see updated tables and structures.Changes
create,drop,alter,truncate,rename), thequerySuccessMsgis flagged withreloadCatalog: true.updateGraphmethod onSidebarViewportfetches the catalog and rebuilds the tree view asynchronously via a Bubble Tea command, so it does not block the UI.updateGraphMsgandupdateGraphErrMsgare introduced to propagate the refreshed tree (or errors) through the Bubble Tea update loop.SidebarViewport.Updatemethod now listens forquerySuccessMsgto trigger a reload and forupdateGraphMsgto swap in the new tree.expandAllmethod call from the sidebar.Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Locally, against databases running on containers.
Checklist: