| PATH |
When you access an enterprise object that has not yet been faulted, Enterprise Objects Framework (EOF) issues a query against the database to load in the object's data. This query loads only the data needed for that particular object. This mechanism normally increases the efficiency of the framework, but it can sometimes be expensive when faulting multiple records.
Batch faulting instructs EOF to fetch data for several objects if any one of them faults. It is useful if you know that when you fetch a particular relationship, you will also fetch other relationships.
In the Movies example database, a Movie has a one-to-one relationship to a PlotSummary. Suppose you have a WOComponent that lets you browse through movies and their summaries in sets of ten. Without batch faulting, EOF will retrieve the PlotSummary data by making ten separate queries to the database every time the component displays a group of Movies. You can use batch faulting to ensure that every time any one of the PlotSummary objects is faulted, nine more are faulted along with it, significantly reducing the number of queries against the database.
The following are three different ways to enable batch faulting.
Use EOModel's batch faulting field in the "Advanced Entity" inspector. This is the easiest way to implement batch faulting, but also the least precise, since EOF chooses which faults to batch. Beware of setting this number too high--EOF may generate a SQL statement that is rejected by the database server.
Don't use batch faulting when reducing memory use is more important than increasing database performance. You may fetch more objects than are needed.
Don't use batch faulting when you know that all the particular relationships for a series of fetched objects will be faulted. Use prefetching instead.