Skip to content

Fix LOGMECH precedence for DATABASE_URI query params #288#296

Merged
dtehan-td merged 2 commits intoTeradata:mainfrom
dtehan-td:bug-288
Apr 14, 2026
Merged

Fix LOGMECH precedence for DATABASE_URI query params #288#296
dtehan-td merged 2 commits intoTeradata:mainfrom
dtehan-td:bug-288

Conversation

@dtehan-td
Copy link
Copy Markdown
Collaborator

Summary

  • Supports LOGMECH (and other query params like ENCRYPTDATA, SSLMODE) specified directly in the DATABASE_URI connection string
  • Establishes clear precedence: CLI arg / env var > URI query param > default TD2
  • Adds _build_query_string() helper to merge extra URI params into all reconstructed SQLAlchemy URLs (main connection, basic auth validation, JWT auth)

Test plan

  • Verify LOGMECH in DATABASE_URI (e.g. teradata://user:pass@host/db?LOGMECH=LDAP) is respected when no --logmech CLI arg or LOGMECH env var is set
  • Verify --logmech CLI arg or LOGMECH env var overrides URI LOGMECH
  • Verify additional URI query params (e.g. ENCRYPTDATA=ON) are propagated to all connection URLs
  • Verify LOGDATA from the original URI is not carried into derived connections

🤖 Generated with Claude Code

@dtehan-td dtehan-td merged commit 7a3b0b5 into Teradata:main Apr 14, 2026
3 checks passed
@dtehan-td dtehan-td deleted the bug-288 branch April 14, 2026 22:05
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