When EGL generates JDBC PreparedStatement objects from your EGL code, you might be able to improve program performance by caching those objects. This improvement is especially likely when you use the same SQL statements repeatedly, such as in a loop or in a frequently called function. For more information about PreparedStatement objects, see prepareAllSQLStatements.
When you generate a program, library, service, or handler with cachePreparedStatements = YES and the code connects to a database, all of the PreparedStatement objects that are used with that connection are cached. The objects are cached even when they are used in a different program, library, service, or handler.
Each database connection has its own cache, and you can specify the size of the cache by setting the preparedStatementCacheSize build descriptor. After one more PreparedStatement object is created than can be placed in the cache, the least recently used object is removed from the cache to make room for the new object.