-
Notifications
You must be signed in to change notification settings - Fork 713
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
schema support? #14
Comments
I think we should support multiple schemata. The simplest approach would be to show all of them all the time. Something nicer may be to show those for which the current user has Basing the list on |
This is an important feature, it is very rare in my experience that I see tables in the default public schema. Usually they are in different schemas with different security definers / policies in place where everything in public schema is the API. |
👍 |
1 similar comment
👍 |
👍 |
I just ran into this problem also. My database doesn't use the public schema, so I can run queries but cannot select any tables. |
yeah,I just ran into this problem also. My database doesn't use the public schema, so I can run queries but cannot select any tables. |
Does this proble solved? |
Is this also the reason why I cannot see materialized views? |
👍 |
👍 I just ran into this problem also. My database doesn't use the public schema, so I can run queries but cannot select any tables. |
hang tight, im working on it. |
👍 if you want help push the branch with your progress or your idea how would you like to implement it, |
👍 Would like this schema support. Willing to help. |
+1 |
Implemented in master |
I can 'set search_path= schema' and run the query through the browsers, but the tables names show in the left do not change.
thanks.
The text was updated successfully, but these errors were encountered: