Skip to content

fix(sql): run the browsed schema, and reorg Db2 indexes by catalog name - #532

Merged
huyplb merged 1 commit into
mainfrom
fix/editor-schema-and-db2-reorg
Oct 15, 2026
Merged

huyplb merged 1 commit into
mainfrom
fix/editor-schema-and-db2-reorg

Conversation

@huyplb

@huyplb huyplb commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Choosing a schema connection checks that one destination. A finished statement starts the next query, and schema. completion lists tables (with aliases) and functions.
  • Expanding a table shows columns only, and the blueprint button is labeled Edit. Access Diff explains the generate-only steps.
  • Db2 index reorg folds the typed schema to the uppercase catalog name, then runs RUNSTATS so the fragmentation percentage can move.

Test plan

  • Index fragmentation and schema-completion unit tests
  • Full dialect e2e sweep (running locally against the app)

Made with Cursor


Note

Medium Risk
Changes destination selection, SQL insertion/completion behavior, and execute error paths; Db2 defrag now issues RUNSTATS with folded identifiers—important for ops but localized to SQL editor and index maintenance.

Reviewed by Cursor Bugbot for commit db48c45. Bugbot is set up for automated code reviews on this repo. Configure here.

Choosing a schema connection checks that destination, a finished statement starts the next query, and schema completion offers tables and functions. Db2 reorg folds the typed schema to the uppercase catalog name and refreshes statistics so the percentage can move.

Co-authored-by: Cursor <cursoragent@cursor.com>
@huyplb
huyplb merged commit 8a0489e into main Oct 15, 2026
11 checks passed
@huyplb
huyplb deleted the fix/editor-schema-and-db2-reorg branch October 15, 2026 15:48
@cursor

cursor Bot commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: ea7f021a-236f-4381-bf74-e9292e690e80)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant