Describe the bug
Prior to latest release of VS Code/SQLTools I was able to view the schema of my Redshift database. Since the upgrade this is longer visible in the SQLTools menu - "Nothing here" text is displayed - see below.

To Reproduce
Steps to reproduce the behavior:
Connections menuSchema within connection - "Nothing here" is displayed instead of a list of tables.Expected behavior
Expanding the Schema option within a db connection allows users to see tables within the schema
Desktop (please complete the following information):
@rjshanahan can you try to manually run this query:
Of course, changing to valid values, let me know if you get any errors
No errors @mtxr ; however, no data returned either.
That said, no results are returned from information_schema.schemata ie. select * from information_schema.schemata limit 10;
what's your postgres version and whats the name of schema?
Here's the version info: PostgreSQL 8.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3), Redshift 1.0.15896.
There's nothing weird in the schema name, eg. abcdef.
Do you still have this issue on recent releases of the driver and the extension?
Hello!
I didn't use the plugin for some time and the driver just got updated. Now I see way less schemas than before.
The data engineer told me that it looks like I only see schemas that the user I'm connected with is owner, even though I'm supposed to see all. Maybe you can check in here?
I'm also experiencing this issue - the schemas listed are only those owned by the current user. I would expect to see all of the schemas shown when running \dn on a psql client logged in as the same user.
Any resolutions to this ?
I'm getting this error as well
The same problem!
Im having the same issue
Same issue here.
Redshift:
PostgreSQL 8.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3), Redshift 1.0.21262
VSCode:
1.51.1
SQLTools:
0.23.0
Have we got a fix for this problem? I'm experiencing the same problem.
seeing same issue. Is there a fix or workaround for this?
having same issue,