Reputation: 311
I recently installed Datagrip to view my Company's Postgres database, however I am currently unable to view the tables in the different schemas by clicking on the schema name:
In the image, I've clicked to open and show the ab-testing
schema, however nothing appears below it. This behavior is consistent across all of the schemas in the database. I am able to use the query editor to query tables in the schemas (assuming i know the table names), yet I cannot see the names in the left-side panel. I am using datagrip 2020.2
Thanks!
Upvotes: 3
Views: 8129
Reputation: 1396
Right click on the "folder" and click "refresh". This has got to be done on the specific folder and not any of it's parents. So drill down to where clicking the chevron doesn't open anything and click "refresh" on that.
Upvotes: 6
Reputation: 1
I've got the same issues and here is my solution and it's work!
(Previously I tried to use Force Refresh but it didn't work and then I found this solution accidentally)
Solution: Try to create a new table with a duplicate name from Database Explorer by following these steps.
Upvotes: 0
Reputation: 21
Right click Microsoft SQL Server in the left pane in Datagrip, then go to "Properties", then"Schemas". Find your database and make sure "All schemas" is ticked.
Upvotes: 2
Reputation: 1113
I had the same problem with a MySQL database. As a test, I used the MariaDB driver instead of the MySQL driver as usual. This was intentional and not an oversight, but it was not a good idea!
The tables, views and server objects were not displayed. Although I was able to display the tables and views after activating Schema Properties -> Advanced -> "Introspect using JDBC metadata", the server objects were not displayed. Working with the displayed tables and views was not possible in the usual way.
Only when I used the MySQL driver again, everything worked correctly again. The tables, views and server objects were displayed correctly and the work with it was possible in the usual way.
As a small quintessence I would like to recommend to all who "struggle" with similar problems to check your chosen drivers. Maybe the problem is caused by choosing the wrong driver, as it was in my case.
Upvotes: 1
Reputation: 1809
Whick kind of message do you get when instrospecting the schema?
I had a java.io.CharConversionException
caused by a not valid UTF-8 string.
If this is the case, you can add the following VM option -Ddb2.jcc.charsetDecoderEncoder=3
.
Upvotes: 0