| 29 | | For large queries that return a large number of data many feature sources support improving performance by configuring the row fetch size in order to reduce the number database hits required to satisfy the selection criteria. For example, Oracle database and Microsoft SQL Server. However, FDO API always returns all data. In this RFC, we will remove this limitation. |
| | 29 | For queries that return a large number of objects many feature sources support improving performance by configuring the row fetch size in order to reduce the number database server round trips required to satisfy the selection criteria. For example, Oracle and Microsoft SQL Server support fetching many rows at once. |
| | 30 | |
| | 31 | While many FDO providers take advantage of this internally, the fetch size they use is fixed and does not allow the caller to tune it based on their circumstances. This enhancement will allow callers to tune the fetch size for providers that will support this. Providers that do not use a fetch size or have a fixed internal implementation simply will ignore the set fetch size. In either case, this does not affect the actual results of queries as it is a performance tuning parameter. |
