The Database Explorer has two options for caching the data in the displays.
Caching will save a lot of time in AQT if you are moving around the Database Explorer. It saves AQT from continually re-fetching information on objects from the database. This can give a significant performance improvement if you are dealing with large databases, plus reduces the load on the network plus database.
The Disk Cache was introduced in AQT v11 and supercedes the History Cache. However the History Cache has been retained as some users may prefer it over the Disk Cache.
The pros and cons of these two caches are as follows:
The options for specifying caching are given in Options > Database Explorer.
History Caching is enabled by default.
When AQT is displaying information from the cache, you will see the following message in the status-bar:
x objects loaded from History buffer. Hit F5 if you need to refresh the data
Hitting F5 (Refresh) will re-fetch the data from the database. You might need to do this if you have created or dropped some objects.
The History icon (above the Object Tree) gives you quick access to your recently displayed objects.
To use this form of caching, go to Options > Database Explorer. Click on Use Disk Cace for Schemas and/or Use Disk Cache for Objects.
When either of these options are used, the History Cache will be disabled.
When AQT has fetched the data from the disk cache, you will get the following messages in the bar at the bottom of the displays.
xx schemas displayed from cache. Hit F6 to refresh
xx objects displayed from cache. Hit F5 to refresh
You may wish to refresh the displays if more schemas or objects have been created. You can do this with F5/F6 or hitting the Refresh buttons above the displays.
Noe: when F6 is hit to refresh the schemas, all the schemas in the Object Tree are refreshed.