📄 sybase.html
字号:
<LI>Read committed
<LI>Repeatable read
<LI>Serializable (the highest level, where
transactions are completely isolated from one another)</LI></UL>
<P>SQLAPI++ maps different isolation levels on
<STRONG>Sybase</STRONG> server in the following way:</P>
<P> <STRONG
>SA_ReadUncommitted</STRONG> = CS_OPT_LEVEL0
('read
uncommitted')<BR><STRONG> SA_ReadCommitted</STRONG> =
CS_OPT_LEVEL1
('read committed')<BR><STRONG> SA_RepeatableRead</STRONG> = CS_OPT_LEVEL2 ('repeatable
read')<BR><STRONG> SA_Serializable</STRONG> =
CS_OPT_LEVEL3
('serializable')</P>
<P>For more details see <A
href="../OnLineDoc/Connection_setIsolationLevel.html">SAConnection::setIsolationLevel</A>.</P>
<P> </P>
<H3><A
name="Working with Long or Lob(CLob, BLob) data">Working with Long or Lob(CLob,
BLob) data</A> </H3>
<P>
SQLAPI++ supports four types for working with
Long or Lob(CLob, BLob) data:</P>
<P>
<TABLE border=1 cellPadding=1 cellSpacing=1 style="WIDTH: 100%"
width=100%>
<TR bgColor=navy>
<TD><FONT color=white
style="BACKGROUND-COLOR: #000080">Name</FONT></TD>
<TD><FONT color=white
style="BACKGROUND-COLOR: #000080">C
enum constant</FONT></TD>
</TR>
<TR>
<TD>LongBinary</TD>
<TD>SA_dtLongBinary</TD>
</TR>
<TR>
<TD>LongChar</TD>
<TD>SA_dtLongChar</TD>
</TR>
<TR>
<TD>BLob (Binary Large object)</TD>
<TD>SA_dtBLob</TD>
</TR>
<TR>
<TD>CLob (Character Large object)</TD>
<TD>SA_dtCLob</TD>
</TR></TABLE></P>
<P>The table below shows how SQLAPI++ data
types correspond with servers original data types:</P>
<P><EM>SA_dtLongBinary</EM> <= > IMAGE<BR><EM>SA_dtLongChar</EM> <= > TEXT<BR
><EM>SA_dtBLob</EM> = >
IMAGE<BR><EM>SA_dtCLob
</EM>=> TEXT</EM></P>
<P>
For more details see <A href="../HowTo/blobs.html">How To - Working with Long or Lob(CLob, BLob) data</A></P>
<P> </P>
<H3><A
name="Returning output parameters">Returning output
parameters</A> </H3>
<p><STRONG>Sybase ASE</STRONG>
server does not provide information about parameter's
direction type, that's why SQLAPI++ Library defines all parameters
(except status result code) as input (SA_ParamInput). If you have
input-output parameters in the procedure you have to call <A
href="../OnLineDoc/Param_setParamDirType.html">SAParam::setParamDirType</A>
method for these parameters before command execution and set
parameter's direction type explicitly.<BR>You
shouldn't call this method for procedure status result code because
it is detected correctly (as SA_ParamReturn) by the Library.</p>
<p>There is no need to call this method for
<STRONG>Sybase ASA</STRONG> because all
parameters are detected correctly automatically (including the
direction type).</p>
<P>For more details see <A
href="../OnLineDoc/Param_setParamDirType.html">SAParam::setParamDirType</A>.</P>
<P>
In <STRONG>Sybase</STRONG>server stored procedures can have integer
return codes and output parameters. The return codes and output
parameters are sent in the last packet from the server and are
therefore not available to the application until all result sets
from stored procedure (if any) are completely processed using <A href="../OnLineDoc/Command_FetchNext.html" >SACommand::FetchNext</A>
method.</P>
<P>SQLAPI++ Library automatically creates <A href="../OnLineDoc/Param.html" >SAParam</A>object to represent procedure
status return code. You can refer to this <A href="../OnLineDoc/Param.html" >SAParam</A> object using SQLAPI++ predefined
name <STRONG>"RETURN_VALUE"</STRONG>.</P>
<P>For more details see <A
href="../OnLineDoc/Command_Execute.html" >SACommand::Execute</A>,
<A href="../OnLineDoc/Param_Usage.html" >SAParam
object</A>, <A
href="../HowTo/return_param.html" >How To - Returning Output Parameters</A>.</P>
<P> </P>
<H3><A name="Cancelling queries">Cancelling
queries</A> </H3>
<P><STRONG>Sybase</STRONG>
does not support queries
cancelling.</P>
<P> </P>
<H3><A name="Connection and command options"><A
name="Connection and command options">Connection, command, parameter and field
options</A><A name="Connection and command options"></A></A>
</H3>
<P>A server specific option can relate to a
connection, command, parameter or field. We recommend you
specify each option in an appropriate object, although it is
possible to specify them in the parental object as well. In that
case the option affects all the child objects. </P>
<P>A connection related option must be specified
in a <A href="../OnLineDoc/Connection.html" >SAConnection</A>
object. </P>
<P>A command related option may be specified in
either <A href="../OnLineDoc/Connection.html">SAConnection</A>
object or <A href="../OnLineDoc/Command.html" >SACommand</A>
object. If it is specified
in <A href="../OnLineDoc/Connection.html" >SAConnection</A>
object it affects all
the commands on that connection. </P>
<P>A parameter related option may be specified in
<A href="../OnLineDoc/Connection.html" >SAConnection</A>
object, <A href="../OnLineDoc/Command.html" >SACommand</A>
object or <A href="../OnLineDoc/Param.html" >SAParam</A>
object. If it is specified in <A href="../OnLineDoc/Connection.html" >SAConnection</A>
object it affects all
the commands and therefore all the parameters on that connection. If
it is specified in <A href="../OnLineDoc/Command.html" >SACommand</A>
object it affects all the
parameters on that command. </P>
<P>A field related option may be specified in
<A href="../OnLineDoc/Connection.html" >SAConnection</A>
object, <A href="../OnLineDoc/Command.html" >SACommand</A>
object or <A href="../OnLineDoc/Field.html" >SAField</A>
object. If it is specified in <A href="../OnLineDoc/Connection.html" >SAConnection</A>
object it affects all
the commands and therefore all the fields on that connection. If it
is specified in <A href="../OnLineDoc/Command.html" >SACommand</A> object it affects all the
fields on that command. </P>
<P>Specific options for <STRONG>Sybase</STRONG>:</P>
<P>
<TABLE border=1 cellPadding=5 width=100%>
<TBODY>
<TR bgColor=#000094>
<TD width=17%>
<P><STRONG><FONT
color=white face="">Option name /
Scope</FONT> </STRONG></P></TD>
<TD>
<P><STRONG><FONT
color=white face="">Description</FONT> </STRONG></P></TD></TR>
<TR>
<TD>
<P align=center>
<STRONG>
CS_PACKETSIZE</STRONG> </P>
<P align=center>Connection related. Should be specified
before actual connection is made.</P>
<TD>
<P>Determines the packet size that Client-Library uses
when sending Tabular Data Stream (TDS) packets. For more
information see Sybase documentation.<BR></P>
<P><EM>Valid values</EM>: String containing
packet size, see Sybase documentation.<BR><EM>Default value</EM>: see Sybase documentation.
</P>
<TR>
<TD>
<P align=center>
<STRONG>
CS_APPNAME</STRONG> </P>
<P align=center>Connection related. Should be specified
before actual connection is made.</P>
<TD>
<P>Defines the application name that a connection will
use when connecting to a
server. For more information see Sybase
documentation. <BR></P>
<P><EM>Valid values</EM>: see Sybase
documentation. <BR
><EM>Default value</EM>: see Sybase
documentation. </P>
<TR>
<TD>
<P align=center>
<STRONG>CS_HOSTNAME</STRONG></P>
<P align=center>
Connection related.
Should be specified before actual connection is
made.</P></TD>
<TD>
<P>Declares the name of the host
machine, used when logging in to a server. For more
information see Sybase documentation. <BR >
</P>
<P><EM>Valid values</EM>: see Sybase
documentation.<BR ><EM>Default value</EM>:
see Sybase documentation.</P></TD></TR>
<TR>
<TD>
<P align=center>
<STRONG>CS_BULK_LOGIN</STRONG></P>
<P align=center>
Connection related.
Should be specified before actual connection is made.</P></TD>
<TD>
<P>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 >
</P>
<P><EM>Valid values</EM>: "CS_TRUE",
"CS_FALSE".<BR ><EM>Default value</EM>:
see Sybase documentation.</P></TD></TR>
<TR>
<TD>
<P align=center>
<STRONG>CS_VERSION</STRONG></P>
<P align=center>
Connection related.
Should be specified before actual connection is made.</P></TD>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -