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

[Bug]: DuckDB - Explorer shows multiple entries for schemas. Tables and Views not populated in their sections. #3666

Closed
usbrandon opened this issue Feb 24, 2024 · 4 comments · Fixed by #3673
Assignees
Labels
Milestone

Comments

@usbrandon
Copy link
Contributor

Apache Hop version?

2.8-SNAPSHOT

Java version?

11

Operating system

Windows

What happened?

image

Issue Priority

Priority: 3

Issue Component

Component: Database

@sramazzina
Copy link
Contributor

@usbrandon we are going to see three different entries per schema name because we have the same set of schema for every catalog defined in DuckDB. In this case, we have 3 catalogs (because is a brand new DuckDB installation) and each catalog has 3 identically named schemas. THis is the reason why you are seeing 3 entries per schema name.

Therefore, apart from an overall improvement to the Database Explorer dialog, in this case a very quick solution could be to disambiguate the schema name by prepending the catalog name. That could be an easy option to better contextualize the things. Let me know what you thing about this.

@hansva @bamaer

@sramazzina
Copy link
Contributor

@usbrandon @hansva @bamaer something like this?

image

@sramazzina
Copy link
Contributor

sramazzina commented Feb 26, 2024

@usbrandon @hansva @bamaer Further refinement...

image

I think thiw way is quick and cleaner enough. What do you think?

@hansva
Copy link
Contributor

hansva commented Feb 26, 2024

LGTM!

sramazzina added a commit to sramazzina/hop that referenced this issue Feb 26, 2024
… Tables and Views not populated in their sections.
sramazzina added a commit to sramazzina/hop that referenced this issue Feb 26, 2024
hansva added a commit that referenced this issue Mar 25, 2024
@hansva hansva added this to the 2.9 milestone Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants