chartdb
Import SQL for single schema
I'd like to try ChartDB with an existing PostgreSQL database I use. In that database there are lots of schemas that I do not use or have access to. I use a few schema, but there is only one schema that I want to visualise with ChartDB.
If I run the PostgresSQL example query to import to ChartDB, it fails because I do not have access to all the schema.
Is there an alternative PostgreSQL query that I can use to try ChartDB with a single named schema?
@andycasey Thank you for opening this issue! We will work to incorporate the option to choose schemas instead of importing all of them at once.
I'd like to try ChartDB with an existing PostgreSQL database I use. In that database there are lots of schemas that I do not use or have access to. I use a few schema, but there is only one schema that I want to visualise with ChartDB.
If I run the PostgresSQL example query to import to ChartDB, it fails because I do not have access to all the schema.
Is there an alternative PostgreSQL query that I can use to try ChartDB with a single named schema?
@andycasey Again, Thanks for bringing this up, and sorry for the inconvenience. We’ve recently added support for filtering schemas, which should solve this issue for you!
Give it a try, and let us know how it goes. We’d love to hear your feedback!
Jonathan
Hi,
Thanks for adding this feature. I'm sure it will help many people, but I can't use this because I cannot even import my database schema to ChartDB, so so I cannot select which schema to show.
There are schema in my database that I do not have permission to access. When I try to import the database using the ChartDB SQL, I get ERROR: permission denied for schema [SCHEMA_NAME]. That means I cannot import ANY of the database into ChartDB in order to test this feature.
Is there a recommended SQL that I should use to import the database schema to ChartDB if I want to exclude specific schema names?
@andycasey Thank you for your feedback! We're glad the new feature is helpful, and I understand the frustration with the permission issue.
We're working on a solution that will allow you to select specific schemas before importing, which should resolve this problem. If you have any suggestions or need further assistance, please let us know!
Stay tuned, and we’ll keep you updated!