| PATH |
EOFetchSpecifications define the way database fetches are performed. They specify such information as the entity to fetch from, which enterprise objects to fetch (a qualifier), the order in which the fetched objects appear (a sort ordering), and other fetch parameters. EOFetchSpecifications are used by an EOEditingContext, the object that actually fetches and maintains the enterprise objects. For more information on fetching, see the programming topics Fetching with an Editing Context and Setting a WODisplayGroup's Fetch Specification Programmatically .
The simplest type of fetch is unqualified and unordered. For example, to create a fetch specification to fetch all of the Movies in the order they appear in the database you use:
EOFetchSpecification fs = new EOFetchSpecification ("Movie",null,null);
To choose which objects to fetch (for example, to fetch all movies starring Harrison Ford) you need to qualify your fetch using an EOQualifier. The programming topic Creating EOQualifiers Programmatically discusses how to build an EOQualifier.
To fetch the objects and sort them in a particular order, you need to specify a sort ordering using EOSortOrdering. The programming topic Creating Sort Orderings discusses how to build an EOSortOrdering.
When you have a qualifier and a sort ordering, you create the fetch specification using:
EOQualifier myQualifier; // assume existsEOSortOrdering mySortOrdering; // assume existsEOFetchSpecification fs = new EOFetchSpecification ("Movie",myQualifier,mySortOrdering);
There are several other parameters that you can set to refine the way a fetch is performed.
Duplicate records sometimes appear in database fetches, usually when the fetch involves joining multiple tables to satisfy the fetch qualifier. The EOFetchSpecification allows you to specify whether you want these duplicate records with the setUsesDistinct method. See the programming topic Fetching Distinct Results for more information.
By default, when you fetch enterprise objects from a database, all objects that match the fetch criteria are returned. For large databases with lots of records, this can mean that users have to wait while all objects are fetched. To avoid this, you can limit the number of objects fetched. The programming topic Setting a Fetch Limit shows how to do this.
Sometimes you know that when you fetch an object, you will always fetch one of its relationships too. By default, EOF fetches the relationship only when you actually traverse it, which results in two fetches (the source object and the relationship). You can improve performance by telling EOF to fetch particular relationships whenever an object is fetched. This is called prefetching and is discussed in the Prefetching programming topic.