Analysis on Toad schema Brower and PLSQL developer's Object Browser

In the previous Java Development, PLSQL developer was used all the time. Search objects (tables, triggers, db_links, synonyms, sequences) were all used in the Object Browser:

Toad was not used until recently when C was used for background service-level development (UNIX). Similar to the above, Toad has a schema Brower. First of all, I have to say, the function is indeed more powerful:

Users can be clearly classified and different definitions can be viewed based on different icons!

In addition, toad can also be viewed based on different views:

Here is a major difference between PLSQL developer and toad:

Sometimes some objects can be found in the PLSQL developer Object Browser, but cannot be found in Toad:

The above two figures are all under the same user. Do you need to select * From all_db_links if you cannot view these objects in toad?

Actually, this is because the schema Brower of Toad has a public node under all schemas:

Find what you want from here? Haha.

I have to say that the toad classification is more reasonable. You can click an object and check the script definition:

 

Description: Db_links and synonyms are widely used in enterprise-level development. If you do not understand this, Google it.