This HTML5 document contains 4 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

Prefix	IRI
n2	http://data.openlinksw.com/oplweb/faq/UDA/WhatDoesUseExtendedFetchDoAnswer#
wdrs	http://www.w3.org/2007/05/powder-s#
schema	http://schema.org/
n6	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n5	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
rdf	http://www.w3.org/1999/02/22-rdf-syntax-ns#
xsdh	http://www.w3.org/2001/XMLSchema#

Statements

Subject Item

n2:this

wdrs:describedby

n5:uda-faq.ttl n6:uda-faq.ttl

rdf:type

schema:Answer

schema:answerExplanation

`Use Extended Fetch'' controls whether Our ODBC Bridge agent/Lite uses the SQLExtendedFetch() function of the underlying ODBC driver, if it's available, when fetching data. Using the bridged driver's SQLExtendedFetch() should improve performance. However it may be necessary to disable this setting- for instance, some drivers do not support extended fetching on a result-set produced by an ODBC catalog call. When extended fetching is disabled, the bridged driver's SQLFetch() function is used instead.