📄 connection_option.html
字号:
<P><STRONG>CS_APPNAME</STRONG><BR>Defines
the application name that a connection will use when
connecting to a server. For more information see Sybase
documentation.<BR>Connection related.
Should be specified before actual connection is made.<BR>
<EM>Valid values</EM>: see Sybase
documentation.<BR><EM>Default
value</EM>: see
Sybase documentation.</P>
<P><STRONG>CS_HOSTNAME</STRONG><BR>Declares
the name of the host machine, used when logging in to a
server. For more information see Sybase
documentation.<BR>Connection related.
Should be specified before actual connection is made.<BR>
<EM>Valid values</EM>: see Sybase
documentation.<BR><EM>Default
value</EM>: see
Sybase documentation.</P> <P >
<STRONG>CS_BULK_LOGIN<BR> </STRONG>Describes whether or not
a connection can perform bulk copy operations into a
database. For information on Bulk Copy, see the Sybase
Common Libraries Reference Manual.
<BR >
Connection related. Should be specified before
actual connection is made.
<BR ><EM>Valid values</EM>: "CS_TRUE",
"CS_FALSE".<BR ><EM>Default
value</EM>: see Sybase documentation.
</P> <P ><STRONG>CS_VERSION</STRONG><BR>Describes the
version of Client-Library behavior that the application
expects. For more information see Sybase documentation.
<BR>Connection related. Should be
specified before actual connection is made. <BR
><EM>Valid values</EM>:
"CS_VERSION_125" (12.5 behavior),
"CS_VERSION_110" (11.0 behavior),
"CS_VERSION_100" (10.0 behavior),
"Detect" (SQLAPI++ automatically detects the
maximum available version of behavior via the version of
Client-Library), "Default" (SQLAPI++ tries to
set 12.5 behavior; if it fails, SQLAPI++ tries to set
11.0 behavior and so on from the highest version to the
lowest one until it succeeds).<BR>
<EM>Default value</EM>: "Default".
</P>
</td>
</tr>
<tr>
<td>
<p><STRONG><A
title="DB2 server specific information" href="../ServerSpecific/DB2.html" >DB2</A></STRONG></p>
</td>
<td>
<p>
None</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>isc_dpb_lc_ctype</STRONG><BR>Specifies the
character set to be utilized. For more information see
InterBase documentation.<BR>Connection related. Should
be specified before actual connection is made.<BR>
<EM>Valid values</EM>: String containing character set name, see
InterBase documentation.<BR><EM>Default
value</EM>: see InterBase documentation.</P>
<P><STRONG>isc_dpb_sql_role_name</STRONG><BR>Declares
role name that should used for connection. For more
information see InterBase documentation.<BR>Connection
related. Should be specified before actual connection is
made.<BR><EM>Valid values</EM>: see InterBase documentation.<BR>
<EM>Default
value</EM>: see InterBase
documentation.</P>
<P><STRONG>isc_dpb_num_buffers</STRONG><BR>Declares the number of database cache buffers
to allocate for use with the database. For more
information see InterBase documentation.<BR>Connection
related. Should be specified before actual connection is
made.<BR><EM>Valid values</EM>: 10-255, see InterBase documentation.<BR
><EM>Default
value</EM>: 75, see InterBase
documentation.</P>
<p><STRONG>CommitRetaining<BR></STRONG>Determines which function (<EM
>isc_commit_transaction()</EM> or
<EM>isc_commit_retaining()</EM>)
SQLAPI++ calls to commit transactions.<BR
><EM>isc_commit_transaction()</EM> writes transaction
changes permanently to a database, closes the result set
associated with the transaction, and frees system
resources assigned to the transaction for other uses.
Active result sets are not preserved.<BR><EM>isc_commit_retaining()</EM> writes all pending
changes to the database, ends the current transaction
without closing its record stream and cursors and
without freeing its system resources, then starts a new
transaction and assigns the existing record streams and
system resources to the new transaction. Active result
sets are preserved. <BR>For more
information see InterBase documentation (<EM
>isc_commit_retaining()</EM> and <EM
>isc_commit_transaction()</EM>
functions). <BR>Connection related. Should
be specified before issuing a commit.<BR
><EM>Valid values</EM>: "true" to
force SQLAPI++ to call <EM>isc_commit_retaining()</EM> function,
"false" to force SQLAPI++ to call <EM
>isc_commit_transaction()</EM>
function.<BR><EM>Default value</EM>:
"false". SQLAPI++ uses <EM>isc_commit_transaction()</EM> function by
default.</p>
<P><STRONG>TPB_LockResolution</STRONG><BR>Describes what
happens if a transaction encounters an access conflict
during a write operation (update and delete operations
on existing rows).<BR>Connection related. Should be
specified before actual connection is made.<BR><EM
>Valid values</EM>:
"isc_tpb_wait" (specifies that the transaction
should wait until locked resources are released; once
the resources are released, the transaction retries its
operation), "isc_tpb_nowait" (specifies that
the transaction should return a lock conflict error
without waiting for locks to be released). <BR
>By default SQLAPI++ doesn't change
InterBase settings for this option. See InterBase
documentation for details.</P>
<P><STRONG>TPB_AccessMode</STRONG><BR>Describes the actions a
transaction can perform against a table.<BR>Connection
related. Should be specified before actual connection is
made.<BR><EM>Valid values</EM>:
"isc_tpb_write" (enables a transaction to read
data from a table and write data to it),
"isc_tpb_read" (restricts table access to read
only). <BR>By default SQLAPI++
doesn't change InterBase settings for this option. See
InterBase documentation for details.</P>
</td>
</tr>
<tr>
<td>
<p><STRONG><A
title="SQLBase server specific information" href="../ServerSpecific/SQLBase.html" >SQLBase</A></STRONG></p>
</td>
<td>
<P>
None</P>
</td>
</tr>
<tr>
<td>
<p><STRONG><A
title="MySQL server specific information" href="../ServerSpecific/MySQL.html" >MySQL</A></STRONG></p>
</td>
<td>
<p> None
</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>
UseDLLonWin32<BR></STRONG>Forces SQLAPI++ Library to use pq.dll or
libpq.dll when you are working on Win32 platform.<BR
>Connection related. Should be specified
before the first connection is
made.<BR><EM>Valid values</EM>: "CygWin" and
"Native".
<BR><EM>Default value</EM>: "Native". SQLAPI++ uses libpq.dll as
the default API DLL.
Setting
"CygWin" value of this option forces SQLAPI++
to use pq.dll.</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>UseManagerOnUNIX<BR></STRONG>Forces
SQLAPI++ Library to use specified library on UNIX.<BR
> Connection
related. Should be specified
before the first connection is made.
<BR
><EM>Valid values</EM>: "<name of
library you want to use>".
<BR><EM>Default value</EM>:
"libiodbc.so.2".
</p>
</td>
</tr>
</table>
<h3>See also</h3>
<p>
<A href="Connection_setOption.html">setOption</A>
</p>
<p>
<A href="Command_Option.html">Command::Option</A>,
<A href="Command_setOption.html">Command::setOption</A>
</p>
<p>
<A href="Command.html">SACommand</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:howto@sqlapi.com">howto@sqlapi.com</A>.
</p>
</td>
<tr></tr>
</table>
</body>
</html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -