Most folks know they can filter their list of Tables.

But did you know you can set a global filter across your entire connection?

two of my connections have global filters applied
two of my connections have global filters applied

It’s pretty basic, but also pretty powerful:

This will filter every node under this connection - tables, indexes, views, procedures, EVERYTHING
This will filter every node under this connection – tables, indexes, views, procedures, EVERYTHING

So how would this be useful?

Maybe for your project or program module, you have all of the objects starting with the same prefix. You can now filter your database objects to just that module or application feature.

These objects all start with 'BEE' so they are being listed.
These objects all start with ‘BEE’ so they are being listed.

These are database side filters – as in – we’re adding and OBJECT_NAME LIKE ‘BEE%’ to the queries used to populate the tree.

You can see this for yourself with thew new Statements log in version 4.1:

These queries could get expensive, use with discretion.
These queries could get expensive, use with discretion.

Each connection can have it’s own filter.

Our Schema Browser has a similar feature – but it’s client-side

It’s always nice to have choices…

No need to wildcard, just type the text you want to filter on.
No need to wildcard, just type the text you want to filter on.
thatjeffsmith
Author

I'm a Master Product Manager at Oracle for Oracle SQL Developer. My mission is to help you and your company be more efficient with our database tools.

Write A Comment