Wiki source code of EOF-Using EOF-Fetch Limits
Last modified by David Holt on 2007/09/18 15:43
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
12.1 | 1 | == Overview == |
| |
4.1 | 2 | |
| |
13.1 | 3 | By default, when you use an EOFetchSpecification, it will fetch all of the EOs that match its EOQualifier. However, often the user interface you will be using is paginated, and there are large performance wins by instead loading your results in pages. |
| |
4.1 | 4 | |
| |
12.1 | 5 | == Core WO == |
| |
4.1 | 6 | |
| |
13.1 | 7 | EOFetchSpecification provides a setFetchLimit(int) method, but it does not directly support pagination, rather it will simply stop returning results after the number specified. This is useful for a cut-and-run approach to querying, but if you need to provide multiple pages of results, you will likely need to look elsewhere. |
| |
4.1 | 8 | |
| |
12.1 | 9 | == Project Wonder == |
| |
4.1 | 10 | |
| 11 | Project Wonder provides several faciliities for addressing this problem: | ||
| 12 | |||
| |
12.1 | 13 | * ERXEOControlUtilities.objectsInRange(ec, fs, start, end) for PostgreSQL, MySQL, and FrontBase |
| |
4.1 | 14 | * ERXBatchingDisplayGroup |
| 15 | * ERXRecursiveBatchFetching | ||
| |
13.1 | 16 | * ERXFetchSpecificationBatchIterator [[Max Muller's original post describing this>>url:http://www.omnigroup.com/mailman/archive/eof/2002/009284.html||shape="rect"]] |