command_option.html

能够连接各种数据库的API

                        size=2><FONT face="" size=3 
                        >DBPROP_SERVERCURSOR, 
                        </FONT></FONT>DBPROP_OTHERINSERT, 
                        DBPROP_OTHERUPDATEDELETE, DBPROP_OWNINSERT, 
                        DBPROP_OWNUPDATEDELETE.</FONT> Some properties can be 
                        safely combined with others. See SQLOLEDB documentation 
                        to get more about how they affect SQL Server cursors. 
                        <BR>Command related. Should be 
                        specified before command execution.<BR><EM>Valid values </EM>  for 
                        <FONT face="" size=2><FONT face="" 
                        size=3>DBPROP_SERVERCURSOR 
                        option</FONT></FONT>: "VARIANT_TRUE" (SQLOLEDB 
                        implements the rowset using a server cursor), 
                        "VARIANT_FALSE" (SQLOLEDB implements the 
                        rowset using a default result set). <BR><EM>Valid values </EM>  for 
                        other<FONT face="" size=2><FONT 
                        face="" size=3> 
                        options</FONT></FONT> : "VARIANT_TRUE", 
                        "VARIANT_FALSE". See&nbsp; SQLOLEDB 
                        documantation for more detailes. <BR>By default SQLAPI++ 
                        doesn't change these options and uses values set by 
                        SQLOLEDB. See SQLOLEDB documentation for details.</P><STRONG>
                        <P><STRONG>DBPROP_COMMANDTIMEOUT<BR></STRONG></STRONG>Sets Command Time Out. <BR 
                        >Command related. Should be specified 
                        before command execution.<BR><EM>Valid values</EM>: String containing number of seconds before a 
                        command times out. A value of "0" indicates an 
                        infinite time-out. <BR>By default 
                        SQLAPI++ doesn't change this option and uses the value 
                        set by SQLOLEDB. See SQLOLEDB documentation for 
                        details.</p>
                        <P><FONT face="" size=3 
                        ><STRONG>Execute_riid</FONT> </STRONG><BR>Sets the requested interface for the rowset 
                        returned by the command. See SQLOLEDB documentation (<EM 
                        >ICommand::Execute()</EM> function) 
                        for details. <BR>Command related. Should be specified 
                        before command execution.<BR><EM 
                        >Valid values</EM> : 
                        "IID_NULL" (no rowset is returned), 
                        "IID_IRowset", "IID_IStream", 
                        "IID_ISequentialStream", 
                        "IID_IMultipleResults". <BR><EM>Default value</EM> : 
                        "IID_IMultipleResults" (to create multiple 
                        results).</P>
		</td></tr>
				<tr>
					<td>
						<p><STRONG><A 
                        title="SQL Server server specific information" href="../ServerSpecific/SQLServer_DbLibrary.html" >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><EM>Valid 
                        values</EM>: "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><EM>Default value</EM>: "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><EM>Valid values</EM>: 
                        "off" and "on".<BR><EM>Default 
                        value</EM>: "off", SQLAPI++ uses dbsqlexec().</p>
					</td>
				</tr>
				<tr>
					<td>
						<p><STRONG><A 
                        title="Sybase server specific information" href="../ServerSpecific/Sybase.html" >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><EM>Valid 
                        values</EM>: String containing number of rows in 
                        the fetch buffer. <BR><EM>Default 
                        value</EM>: "1".</P>
					</td>
				</tr>
				<tr>
					<td>
						<p><STRONG><A 
                        title="DB2 server specific information" href="../ServerSpecific/DB2.html" >DB2</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><EM>Valid 
                        values</EM>: String 
                        containing number of rows in the fetch buffer. <BR><EM>Default 
                        value</EM>: "1".</P>
                        
                        <P><STRONG>ReturnStatus<BR></STRONG>DB2 stored procedures 
                        always return a value, and SQLAPI++ automatically 
                        creates <STRONG>SAParam</STRONG> 
                        object to represent the function return value. This 
                        option allows to cancel creating this <STRONG 
                        >SAParam</STRONG> object. <BR 
                        >Command related. Should be 
                        specified before describing parameters or command 
                        execution.<BR><EM>Valid values</EM>: 
                        "Ignore" (SQLAPI++ does not create 
                        <STRONG>SAParam</STRONG> object to 
                        represent function return value), "Default" 
                        (SQLAPI++ creates <STRONG>SAParam</STRONG> object to represent function 
                        return value). <BR><EM>Default value</EM>: "Default".</P>
					</td>
				</tr>
				<tr>
					<td>
						<p><STRONG><A 
                        title="Informix server specific information" href="../ServerSpecific/Informix.html" >Informix</A></STRONG></p>
					</td>
					<td>
						<p> 
                           None</p>
					</td>
				</tr>
				<tr>
					<td>
						<p><STRONG><A 
                        title="InterBase server specific information" href="../ServerSpecific/InterBase.html" >InterBase</A></STRONG></p>
					</td>
					<td>
                        <P><STRONG>SQLDialect</STRONG><BR>Declares the SQL Dialect for database access.<BR>Command related.<BR><EM>Valid 
                        values</EM>: see InterBase documentation.<BR><EM>Default value</EM>  is "3".</P>
					</td>
				</tr>
				<tr>
					<td>
						<p><STRONG><A 
                        title="SQLBase server specific information" href="../ServerSpecific/SQLBase.html" >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><EM>Valid values</EM>: 
                        "off" and "on".<BR><EM>Default value</EM>: see SQLBase documentation.</P>
                        <P><STRONG><STRONG>StoredObject<BR></STRONG></STRONG>If you call 
                        stored command you can set this option to 
                        "Command" value. It allows SQLAPI++ to 
                        optimize stored command execution. <BR>Command related. <BR>
                        <EM>Valid values</EM>: "Procedure" and "Command". 
                        <BR><EM>Default value</EM>: "Procedure".</P>
					</td>
				</tr>
				<tr>
					<td>
						<p><STRONG><A 
                        title="MySQL server specific information" href="../ServerSpecific/MySQL.html" >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><EM>Valid values</EM>: 
                        "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><EM>Default value</EM>: 
                        "use". </p>
					</td>
				</tr>
				<tr>
					<td>
						<p><STRONG><A 
                        title="PostgreSQL server specific information" href="../ServerSpecific/PostgreSQL.html" >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>
                        <EM>Valid values</EM>: "LargeObject" and "Oid". <BR 
                        ><EM>Default 
                        value</EM>: 
                        "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 
                        title="ODBC server specific information" href="../ServerSpecific/ODBC.html" >ODBC</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><EM>Valid 
            values</EM>: String containing number of rows in the fetch buffer. 
            <BR><EM>Default value</EM>: "1".</P>
					</td>
				</tr>
</table>
			
			<h3>See also</h3>
			<p>
			<A href="Command_setOption.html">setOption</A> 
			</p>
			<p>
			<A href="Connection_Option.html">SAConnection::Option</A>, 
			<A href="Connection_setOption.html">SAConnection::setOption</A> 
			</p>
			<p>
			<A href="Connection.html">SAConnection</A>,   
			<A href="String.html">SAString</A> 
			</p>

			<h3>Problems and Questions</h3>
			<p>
			If you haven't found the answer to your 
            questions or have some problems on using the Library, please, send 
            e-mail to <A href="mailto:[e-mail]">[e-mail]</A>. 
			</p></TD>
	<tr></tr></TBODY></TABLE>
</body>
</html>