Cannot find a database object in Database tool window

If someone changed the remote database data or view, the local view of the database might differ from the actual state of the database.

note

If you see no schemas in the popup, check whether a connection to a data source is available. For more information, refer to this troubleshooting article or report the situation to us.

When you create a data source, the data source is created with no schemas selected. You need to select schemas with which you plan to work.

To select the schemas, do one of the following:

The Default schema or Default database is a schema or a database that will be current in connection to a data source. The current schema is a schema that is current in a session. You can change the current schema by using SET CURRENT_SCHEMA. The default schema depends on database settings and data source settings that you set in the JDBC URL.

You can change this default in connection settings of a data source. To change the default, click the Data Source Properties icon in the Database tool window (View | Tool Windows | Database). From the list of data sources, select your data source. In the Database field, type the name of a schema or a database that you want to use as a default.

If the items of the object kind are filtered out from the view, the objects wil be hidden in the Database tool window.

To make sure the database object is not filtered out from the view, do the following:

1. In the Database tool window toolbar, click View Options.

2. Select Filter.

3. Navigate to the database object kind and make sure that the checkbox is ticked.

The green dot in the corner of filter icon indicates that the filter is on and some objects are filtered out.

Everything is filtered out except views and tables

Nothing is filtered out

The Force Refresh action clears the data source information from cache and loads it again from scratch.

To profile the introspection and diagnose possible issues, CLion can generate three files that include information about the following:

• dataSource.txt: the data source.

• introspector.txt: a module that was used to load the metadata from the database.

• model.xml: a part of the database model.

This information might be helpful when introspection works incorrectly. For example, when you see something outdated or do not see new objects.

1. Right-click a data source and navigate to Diagnostics | Generate Introspector Diagnostic Files.

2. CLion will generate three files with the introspector diagnostic info.

   

   Click the link in the Diagnostic information collected notification message to navigate to the directory with generated files.

The following screenshots show the example output of these three files.

• dataSource.txt

  

• introspector.txt

  

• model.xml

  

warning

Switch to the JDBC-based introspector with caution and when requested by the JetBrains support team. This step may lead to problems with code generation because some objects and properties become unavailable or return wrong values.

Consider this step as a temporary workaround. If you cannot see objects in the Database tool window, you might have a bug. Collect troubleshooting materials and send them to our support team.