The driver can implement a client-side data cache for improved performance. Data is cached from the remote data source to the local machine on which the driver is located.
The driver caches data on a per-table basis, as opposed to caching the result of a particular query. Caching data on a table level allows the caches to be queried, filtered, and sorted in other queries. Once a cache is created, its use is transparent to the application. For example, if a cache is created on the Account table, then all subsequent queries that reference Account access the Account cache. Disabling or dropping the cache gives references to the Account table access to the remote data again. Because the use of the cache is transparent, no changes to the application are required to take advantage of the cache.
You must specifically create a cache before it can be populated; caches are not created automatically. After you have created a cache on a table, the cache will be populated as a result of the next operation on the table. For example, after creating a cache on Account, data is returned from the data source and stored locally in the cache when you first execute the following statement:
SELECT ROWID, SYS_LOOKUPNAME FROM Account
Any subsequent queries against the Account table return data from the cache, which reduces response time. SQL queries can access both cached data and remote data (data stored in the data source that has not been assigned to a cache) in the same statement.
To create, modify, refresh, or delete client-side data caches, use the following SQL statement extensions:
Create Cache
