📄 command_setoption.html
字号:
performance in fetching data;<BR>- support only one active statement at a time
on a connection.
<LI>Server cursors, which:<BR
>- support multiple active
statements on a single connection;<BR>- can decrease performance relative to a
default result set.</LI></UL>
<P>See SQLOLEDB documentation to
get more about differences between the default result
sets and server cursors. <BR>Command related. Should be specified before
command execution.<BR>Valid values:
"VARIANT_TRUE" (SQLOLEDB implements the rowset
using a server cursor), "VARIANT_FALSE"
(SQLOLEDB implements the rowset using a default result
set). <BR>Default value is
not set. In this case the rowset is implemented using a
default result set.</P>
</td>
</tr>
<tr>
<td>
<p><STRONG><A
href="../ServerSpecific/SQLServer_DbLibrary.html" title="SQL Server (DB-Library) specific information">SQL
Server (DB-Library)</A>
</STRONG> </p>
</td>
<td>
<p><STRONG>OpenCursor</STRONG><BR
>Forces SQLAPI++ Library to use
DB-Library cursor functions to process the command
execution result set. It allows to open several result
sets simultaneously in one transaction. For more
information see SQLServer (DB-Library) documentation.<BR
>Command related. <BR>Valid
values: "number of rows[, scroll option]".
String containing number of rows in the fetch buffer and
(optional) scroll option. Valid values for scroll option
are: CUR_DYNAMIC, CUR_FORWARD, CUR_KEYSET,
CUR_INSENSITIVE. If scroll option parameter is omitted then CUR_FORWARD value is used.
For more information see DB-Library documentation.<BR
>Default value: "0".
"0" means that the command doesn't use a
cursor to process its statement.</p>
<p><STRONG>UseDataReadyLoopOnExecute</STRONG><BR>Forces SQLAPI++ Library to use DB-Library
dbsqlsend() + dbdataready() loop + dbsqlok() instead of
dbsqlexec() when executing a query. Works slower but
allows query cancellation from another
thread.<BR>Command related.<BR>Valid
values: "off" and "on".<BR
>Default value: "off",
SQLAPI++ uses dbsqlexec().</p>
</td>
</tr>
<tr>
<td>
<p><STRONG><A
href="../ServerSpecific/Sybase.html" title="Sybase server specific information">Sybase</A></STRONG></p>
</td>
<td>
<P><STRONG>PreFetchRows</STRONG><BR>Forces SQLAPI++
Library to fetch rows in bulk, rather than retrieving
records one by one.<BR>Command
related. Should be specified before command
execution.
<BR>
Valid values: String
containing number of rows in the fetch buffer.
<BR>
Default value: "1".</P>
</td>
</tr>
<tr>
<td>
<p><STRONG><A
href="../ServerSpecific/DB2.html" title="DB2 server specific information">DB2</A></STRONG></p>
</td>
<td>
<p>
None</p>
</td>
</tr>
<tr>
<td>
<p><STRONG><A
href="../ServerSpecific/Informix.html" title="Informix server specific information">Informix</A></STRONG></p>
</td>
<td>
<p>
None</p>
</td>
</tr>
<tr>
<td>
<p><STRONG><A
href="../ServerSpecific/InterBase.html" title="InterBase server specific information">InterBase</A></STRONG></p>
</td>
<td>
<P><STRONG>SQLDialect</STRONG><BR>Declares
the SQL Dialect for database access.<BR>Command related.<BR>Valid
values: see InterBase documentation.<BR>Default value is "3".</P>
</td>
</tr>
<tr>
<td>
<p><STRONG><A
href="../ServerSpecific/SQLBase.html" title="SQLBase server specific information">SQLBase</A></STRONG></p>
</td>
<td>
<P><STRONG>SQLPPCX</STRONG><BR>Controls
cursor-context preservation. For more information see
SQLBase documentation.<BR>Command
related.<BR>Valid values:
"off" and "on".<BR>Default value: see SQLBase documentation.</P>
</td>
</tr>
<tr>
<td>
<p><STRONG><A
href="../ServerSpecific/MySQL.html" title="MySQL server specific information">MySQL</A></STRONG></p>
</td>
<td>
<p>
<STRONG
>HandleResult<BR></STRONG>Determines whether the
result set will be stored in a temporary table or local
bufer on a client (it allows to open several result sets
simultaneously in one transaction), or it will be read
row by row directly from the server (somewhat faster and
uses much less memory). For more information see MySQL
documentation (<EM>mysql_store_result()</EM> and
<EM>mysql_use_result()</EM>
functions). <BR>
Command related.
Should be specified before command
execution.<BR>Valid values:
"use" to force SQLAPI++ to call
<EM>mysql_use_result()</EM> function, "store"
to force SQLAPI++ to call <EM>mysql_store_result()</EM>
function.<BR>Default value:
"use".</p>
</td>
</tr>
<tr>
<td>
<p><STRONG><A
href="../ServerSpecific/PostgreSQL.html" title="PostgreSQL server specific information">PostgreSQL</A></STRONG></p>
</td>
<td>
<P><STRONG>OidTypeInterpretation</STRONG><BR>Forces SQLAPI++
Library to interpret fields of Oid type as an object
identifier or a Large Object.<BR>Command related. <BR>Valid
values: "LargeObject" and "Oid". <BR
>Default value:
"Oid".<BR>After you set
"LargeObject" value to this option, SQLAPI++
interprets Oid type fields data as BLob data. Otherwise,
it reads them as object identifiers (as ordinary
numbers).</P>
</td>
</tr>
<tr>
<td>
<p><STRONG><A
href="../ServerSpecific/ODBC.html" title="ODBC server specific information">ODBC</A></STRONG></p>
</td>
<td>
<p> None</p>
</td>
</tr>
</table>
<h3>See also</h3>
<p>
<A href="Command_Option.html">Option</A>
</p>
<p>
<A href="Connection_setOption.html">SAConnection::setOption</A>,
<A href="Connection_Option.html">SAConnection::Option</A>
</p>
<p>
<A href="Connection.html">SAConnection</A>,
<A href="String.html">SAString</A>
</p>
<h3>Problems and Questions</h3>
<p>
If you don't find the answer to you questions
or have some problems on using the Library, please, send e-mail to <A href="mailto:howto@sqlapi.com">howto@sqlapi.com</A>.
</p>
</td>
<tr></tr>
</table>
</body>
</html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -