You can access this panel from the ‘View‘ menu. It’s a good bit down the screen, so I don’t blame you if you haven’t seen it before. It makes finding ‘stuff’ in your database so much easier. Let’s say I want to find my ‘beer’ objects.
I simply need to type my search string and the context (in this case I want it to search EVERYTHING), and hit enter.
The search results are listed below and clicking on an object automatically opens it!
I know it seems very simple, but I get asked this question a LOT.
Finding too much? Be sure to toggle off the ‘%’ wildcard check box before doing a search.
Working on a Project?
I bet you use common column names, or codes, throughout your tables. You could take advantage of this knowledge and use the Find Database Object panel as a substitute connection tree or schema browser. Working on your HR project and want to look at your employee objects? Do a column search for your column ID/key.
Sometimes thinking outside the box actually works!
Don’t be afraid to tackle a problem from a weird angle, or re-purpose your tools. I do it all the time
And I drive the developers nuts trying to do things with the tools they were never designed to do. But I digress. Back to your coding!




Twitter
RSS
GooglePlus
Facebook
Sep 13, 2012 @ 09:21:17
“It will even search through your PL/SQL code!” – is relative.
It finds declaration of variables in packages and other stored Pl/SQL modules using the content of “Name” field, but doesn’t fine declaration of functions and procedures in the same packages. That is really pity. It looks like the definition of term “Object” is not fully extended to cover procedures and functions declared within packages. Finding such “internal objects” is much more helpful as finding local variables in stored procedures.
Sep 13, 2012 @ 15:06:05
I knew that line was going to get me in trouble. And you’re right, we don’t search ALL_SOURCE, we instead look at views like ALL_ARGUMENTS. We’re going to fix that. And I’ll try to send you a note when it’s available to you.