Skip to content

fix(db2): Windows login / empty schema so table edit works again - #115

Merged
huyplb merged 1 commit into
mainfrom
cursor/ibm-windows-login-7e48
Jul 28, 2026
Merged

fix(db2): Windows login / empty schema so table edit works again#115
huyplb merged 1 commit into
mainfrom
cursor/ibm-windows-login-7e48

Conversation

@huyplb

@huyplb huyplb commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Summary

Refocuses on the IBM DB2 Windows login issue (this agent’s original scope). After a bad login / empty schema load, the SQL explorer shows no tables — so table edit / blueprint looks “gone”.

Fixes

  • Always rebuild DB2 connection strings with Authentication=SERVER (core + frontend delegate)
  • ODBC-brace escape for passwords containing ; / }
  • On Windows, strip conflicting IBM\gsk8 PATH entries when wiring clidriver
  • Clear error when ibm_db is present but installer/clidriver is missing
  • /schema/load returns 400 when a schemaRequired dialect (DB2) has no schema selected
  • foxschema drivers install db2 uses --foreground-scripts (same as the UI installer)

Test plan

  • Unit: db2.connection.test.ts, db2.env.test.ts
  • cd apps/web && npx tsc --noEmit
  • On Windows: reinstall driver if needed (foxschema drivers install db2 or UI install), pick a schema, confirm tables + blueprint edit appear
Open in Web Open in Cursor 

IBM DB2 on Windows often connected without Authentication=SERVER, lost
passwords containing ';', or skipped clidriver install scripts — then
schema load returned zero tables and table edit looked missing.

- Always rebuild DB2 strings with Authentication=SERVER; ODBC-brace PWD
- Strip IBM GSKit from PATH; clear error when clidriver is missing
- Require schema on /schema/load for schemaRequired dialects
- foxschema drivers install db2 uses --foreground-scripts like the UI

Co-authored-by: huy.phan9 <huyplb@users.noreply.github.com>
@huyplb
huyplb marked this pull request as ready for review July 28, 2026 05:30
@huyplb
huyplb merged commit bf56795 into main Jul 28, 2026
5 of 6 checks passed
@cursor

cursor Bot commented Jul 28, 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: serverGenReqId_e4d1403d-0cee-4cb8-92b9-333a1d01bf9b)

@huyplb
huyplb deleted the cursor/ibm-windows-login-7e48 branch July 28, 2026 05:30
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.

2 participants