feat(python): support named database connections - #11
Merged
Conversation
JaviMaligno
force-pushed
the
feat/multi-database-python
branch
from
July 30, 2026 06:45
e2b83e1 to
034a7ba
Compare
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
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
list_databasesand optionaldatabaseon all 14 database toolsVerification
uv run ruff format --check .uv run ruff check .uv run pytest -q(77 passed, 18 integration tests skipped without credentials)uv run pytest --run-integration -qagainst Azure PostgreSQL (95 passed)uv buildStack
This PR is intentionally based on
feat/multi-database-typescript/ #10. Merge #10 first, then retarget or merge this PR.Closes #5 after the parent PR and this PR are merged.
Contributes the Python SDK v2 portion of #4.