Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Support fetching multiple databases and schemas and their associated tables #835

Conversation

guenp
Copy link
Contributor

@guenp guenp commented Dec 5, 2023

Picking this up from previous PRs by @Mause and @Alex-Monahan (see #748 and #740)

Due to having multiple databases in DuckDB, the Postgres dialect of get_schema_names has duplicates (Ex: one copy of "main" for every database, including temp and system).

This change adds a method get_schema_names that returns a list of schema names formatted as <db name>.<schema name> and lets you get a schema's associated tables using get_table_names.

@Mause
Copy link
Owner

Mause commented Dec 5, 2023

Are you able to look at the failing checks?

@guenp guenp changed the title Support fetching multiple databases and schemas and their associated tables fix: Support fetching multiple databases and schemas and their associated tables Dec 6, 2023
@guenp
Copy link
Contributor Author

guenp commented Dec 6, 2023

@Mause, sure thing, I think all checks are passing now.

@guenp
Copy link
Contributor Author

guenp commented Dec 6, 2023

Alright, I was able to repro the test failure locally and I think I fixed it now! Just to be 100% sure I ran the CI pipeline here: https://github.com/motherduckdb/duckdb_engine/actions/runs/7118602752.

@guenp
Copy link
Contributor Author

guenp commented Dec 8, 2023

@Mause This is now ready for review

@Mause Mause merged commit 8e538ce into Mause:main Dec 9, 2023
11 checks passed
@Mause
Copy link
Owner

Mause commented Dec 9, 2023

Thanks! This is now released in 0.9.4

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.

3 participants