feat(XS-53): Object DDL and a deeper schema tree - #65
Merged
Conversation
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.
📝 What changed?
The schema tree now continues past columns into indexes, constraints and triggers per table, with functions and procedures closing each schema and views marked apart from tables. Right-clicking any object offers Copy DDL and Open DDL in new tab - SQLite and MySQL/MariaDB return the engine's own text, while PostgreSQL's
CREATE TABLEis composed from the catalog because it has noSHOW CREATE TABLE.🧩 Change type
🧠 Impact
📊 SQL impact (if relevant)
🧪 Tested
cd frontend && npm test)wails3 task test)wails3 task e2e:go:all)wails3 task e2e:ui:all) - local only, not in CI📌 Notes