fix(db2): Windows login / empty schema so table edit works again#115
Draft
huyplb wants to merge 1 commit into
Draft
fix(db2): Windows login / empty schema so table edit works again#115huyplb wants to merge 1 commit into
huyplb wants to merge 1 commit into
Conversation
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>
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
2 participants
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.
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
Authentication=SERVER(core + frontend delegate);/}IBM\gsk8PATH entries when wiring clidriveribm_dbis present butinstaller/clidriveris missing/schema/loadreturns 400 when aschemaRequireddialect (DB2) has no schema selectedfoxschema drivers install db2uses--foreground-scripts(same as the UI installer)Test plan
db2.connection.test.ts,db2.env.test.tscd apps/web && npx tsc --noEmitfoxschema drivers install db2or UI install), pick a schema, confirm tables + blueprint edit appear