Understanding Database Filters

You can filter schemas, database object types, and database objects within a type, so that a subset that you define is displayed in the Connection Navigator. This is useful in environments where there may be thousands of schemas accessible from a connection, for example.

When you create a connection to an Oracle database, JDeveloper filters out all schemas except the one named in the connection by default. You can change this default filtering anytime after expanding the default schema node, once per JDeveloper startup. If you connect via third-party JDBC or JDBC-ODBC connections, all schemas are shown.

You can define a filter for schemas in a connection, or for any set of object types (Tables, Views, etc.) within a schema, or for any set of objects within an object type folder (for example, display only the tables that begin with DB).

To identify filters currently applied:

Select View | Connection Navigator.
In the Connection Navigator, select Database .
Expand Database, then select a connection, and expand it if it has not yet been loaded. Filtering is not available until the connection has been loaded (once per connection per JDeveloper session).
Select a connection, schema within a connection, or folder within a schema:

If a filter is currently applied to the selection, a filter icon appears on the node of the selected object:

With the object still selected, click the filter icon in the Connection Navigator toolbar and a dialog appears, showing the current selection, if any. From this dialog, you can change the filter currently applied.