Many of the aforementioned Kodo interfaces give you access to a kodo.runtime.FetchConfiguration instance. The FetchConfiguration allows you to exercise some control over how objects are fetched from the data store, including large result set support , custom fetch groups, and lock levels. You can cast any fetch configuration Kodo returns to its JDBC-specific subclass, the kodo.jdbc.runtime.JDBCFetchConfiguration. See its Javadoc for details.

Fetch configurations are passed on from parent components to child components. The persistence manager factory settings (via the configuration properties) for things like the fetch batch size, result set type, and custom fetch groups are passed on to the fetch configuration of the persistence managers it produces. The settings of each persistence manager, in turn, are passed on to all queries and extents it returns. Note that the opposite, however, is not true. Modifying the fetch configuration of a query or extent does not affect the persistence manager's configuration. Likewise, modifying a persistence manager's configuration does not affect the persistence manager factory.