The Connection Tree and Schema Browser make pretty nifty object navigators. But maybe you want your own custom list of objects.
Perhaps you’re working on a project and you only want to see objects that pertain to Project XYZ. And you’re able to ID these objects by a common column ID – or use your imagination and think of some other meta bit or byte.
It could look a little something like this:
I simply made a user defined report, and docked it where my connection panel is.
The not so simple bit, I wrapped the object name, object type, and schema bits with some custom TEXT that SQL Developer knows to render as an object navigator link/URL.
The important bits…
SELECT owner SCHEMA, 'SQLDEV:LINK:' ||owner ||':' ||object_type ||':' ||object_name ||':oracle.dbtools.raptor.controls.grid.DefaultDrillLink' TABLES FROM DBA...
If I refresh the report, it will prompt me for the text I want to match tables on, in this case, I’m looking for columns from DBA_TAB_COLS where COLUMN_NAME like :TEXT.
In the screenshot, I’ve supplied %EMP% to find any table in the database that has at least column name containing the string ‘EMP.’
My SQL is ugly, so I’m not going to share it. I’ve shared the important bits already – the secret sauce to getting the object navigators to work, and I’ve reminded you that reports are frigging awesome, and that you can doc them wherever you want.
This is another good way to freak our your co-workers and remind THEM how frigging awesome YOU are 🙂
One last thing…
Reports are wonderful. The grids are filterable, searchable, exportable, all kinds of ‘able.’ You could also create child reports showing said columns for each table or even one called Views that showed you the views you wanted to see.