📄 mysql.html
字号:
types correspond with servers original data types:</P>
<P><EM>SA_dtLongBinary</EM> <= > BLOB<BR><EM>SA_dtLongChar</EM> <= > TEXT<BR
><EM>SA_dtBLob</EM> = >
BLOB<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> MySQL</STRONG>
server does not support stored procedures.</p>
<P> </P>
<H3><A name="Cancelling queries">Cancelling
queries</A> </H3>
<P>Using <A href="../OnLineDoc/Command_Cancel.html" >SACommand::Cancel</A> method you
can cancel the following types of processing on a statement:</P>
<UL type=disc>
<LI>A function running asynchronously on
the statement.<BR>
<LI>A function running on the statement on
another thread. </LI></UL>
<p>SQLAPI++ calls <STRONG>mysql_kill</STRONG> function to cancel a query, and then calls
<STRONG>mysql_ping</STRONG> function to restore connection with server. To get more
details see <STRONG>mysql_kill</STRONG> and <STRONG>mysql_ping</STRONG> functions
description in <STRONG>MySQL</STRONG>
documentation.</p>
<P>For more details see <A href="../OnLineDoc/Command_Cancel.html" >SACommand::Cancel</A>.</P>
<P> </P>
<H3><A
name="Connection and command options">Connection and command
options</A>
</H3>
<P>A server specific option can be related with
a command or with a connection. A connection related option must be
specified in a <A href="../OnLineDoc/Connection.html" >SAConnection</A>
object. A command
related option may be specified in either <A href="../OnLineDoc/Connection.html" >SAConnection</A>
object
or <A href="../OnLineDoc/Command_Usage.html" >SACommand</A>
object. </P>
<P>Specific options for <STRONG>MySQL</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</FONT> </STRONG></P></TD>
<TD>
<P><STRONG><FONT
color=white face="">Description</FONT> </STRONG></P></TD></TR>
<TR>
<TD>
<STRONG>
HandleResult</STRONG></TD>
<TD>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><STRONG>Command related.</STRONG>
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".
</TD>
</TR>
</TBODY>
</TABLE>
</P>
<P>For more details see <A href="../OnLineDoc/Command_setOption.html" >SACommand::setOption</A>, <A href="../OnLineDoc/Connection_setOption.html" >SAConnection::setOption</A>.</P>
<P> </P>
<H3><A name="Getting native MySQL API">Getting
native MySQL API</A> </H3>
<P>You can call client specific API functions
which are not directly supported by SQLAPI++ Library. <A
href="../OnLineDoc/Connection_NativeAPI.html">SAConnection::NativeAPI</A>
method returns a pointer to the set of native API functions
available for <STRONG>MySQL</STRONG>
. To use the database API directly you have to downcast
this <STRONG>saAPI</STRONG> pointer to the appropriate type and use its
implementation-specific members. The following table shows what type
cast you have to make and what additional header file you have to
include to work with <STRONG>MySQL</STRONG>
API. </P>
<P>
<TABLE border=1 cellPadding=5 width=100%>
<TR bgColor=#000094>
<TD style="WIDTH: 300px" width=300>
<P><STRONG><FONT color=white face="">Type casting</FONT>
</STRONG></P></TD>
<TD>
<P><STRONG><FONT color=white face="">Additional
<BR>include
file</FONT> </STRONG></P></TD></TR>
<TR>
<TD>
<P>Cast the result to <STRONG
>class myAPI</STRONG>:</P>
<P><FONT face=System>saAPI *pResult = con.NativeAPI();<BR>myAPI *p_myAPI = (myAPI *)pResult;</FONT></P></TD>
<TD><STRONG>
<P><STRONG>#include
<myAPI.h></STRONG></P> </STRONG></TD></TR>
</TABLE> </P>
<P>To get more information about DBMS API
functions see this DBMS specific documentation. </P>
<P>For more details see <A
href="../OnLineDoc/Connection_NativeAPI.html">SAConnection::NativeAPI</A>.</P>
<P> </P>
<H3><A
name="Getting native MySQL connection related handles">Getting
native MySQL connection related handles</A> </H3>
<P>You have to use native API handles when you
want to call specific <STRONG>MySQL</STRONG>
API functions which are not directly
supported by the Library. API functions usually need to receive one
or more active handles as a parameter(s). <A
href="../OnLineDoc/Connection_NativeHandles.html">SAConnection::NativeHandles</A> method returns a pointer to
the set of native API <STRONG>connection
related</STRONG> handles. To use API handles directly you have to
downcast <STRONG>saConnectionHandles</STRONG> pointer to the appropriate type
and use its implementation-specific members. The following table
shows what type cast you have to make and what additional header
file you have to include to work with specific
<STRONG>MySQL</STRONG>
API. </P>
<p>
<table border=1 cellPadding=5 width=100%>
<TBODY>
<tr bgColor=#000094>
<td >
<P><STRONG><FONT color=white face="">Type casting</FONT> </STRONG></P></td>
</tr>
<TR>
<TD>
<P><STRONG><FONT color=maroon
face="">Cast the result</FONT></STRONG> to <STRONG
>class
myConnectionHandles</STRONG>:</P><FONT face=System><FONT face=System>
<P><STRONG><FONT color=maroon face="">#include
<myAPI.h></FONT> </STRONG></P>
<P>saConnectionHandles *pResult =
con.NativeHandles</FONT>();<BR>myConnectionHandles *p_myCH
=<BR>
(myConnectionHandles *)pResult;</p>
<P><FONT
face="Times New Roman"><STRONG><FONT color=maroon
face="">Available handles:</FONT></STRONG></FONT>
</P>
<UL>
<LI><FONT face="Times New Roman">MYSQL
*mysql;</FONT>
</FONT></LI></UL></td></tr>
</table></P>
<P>To get more information about DBMS API
functions and handles see this DBMS specific documentation.
</P>
<P>For more details see <A
href="../OnLineDoc/Connection_NativeHandles.html">SAConnection::NativeHandles</A>.</P>
<P> </P>
<H3><A
name="Getting native MySQL command related handles">Getting native
MySQL command related handles</A> </H3>
<P>You have to use native API handles when you
want to call specific <STRONG>MySQL</STRONG>
API functions which are not directly
supported by the Library. API functions usually need to receive one
or more active handles as a parameter(s). <A
href="../OnLineDoc/Command_NativeHandles.html">SACommand::NativeHandles</A> method returns a pointer to the
set of native API <STRONG>command
related</STRONG> handles. To use API handles directly you have to
downcast <STRONG>saCommandHandles</STRONG> pointer to the appropriate type and
use its implementation-specific members. The following table shows
what type cast you have to make and what additional header file you
have to include to work with specific <STRONG>MySQL</STRONG>
API. </P>
<p>
<table border=1 cellPadding=5 width=100%>
<TBODY>
<tr bgColor=#000094>
<td >
<P><STRONG><FONT color=white face="">Type casting</FONT> </STRONG></P></td>
</tr>
<TR>
<TD>
<P><STRONG><FONT color=maroon
face="">Cast the result</FONT></STRONG> to <STRONG
>class
myCommandHandles</STRONG>:</P><FONT face=System><FONT face=System>
<P><STRONG><FONT color=maroon face="">#include
<myAPI.h></FONT> </STRONG></P>
<P>saCommandHandles *pResult =
cmd.NativeHandles</FONT>();<BR>myCommandHandles *p_myCH
=<BR>
(myCommandHandles *)pResult;</p>
<P><FONT
face="Times New Roman"><STRONG><FONT color=maroon
face="">Available handles:</FONT></STRONG></FONT>
</P>
<UL>
<LI><FONT face="Times New Roman"> MYSQL_RES
*result;</FONT></LI></UL></FONT></TD></TR></TBODY></TABLE></P>
<P>To get more information about DBMS API
functions and handles see this DBMS specific documentation.
</P>
<P>For more details see <A
href="../OnLineDoc/Command_NativeHandles.html">SACommand::NativeHandles</A>.</P>
<P> </P>
<H3><A name="Error handling">Error
handling</A> </H3>
<P>When an error occurs inside SQLAPI++ Library
it throws an exception of type <A href="../OnLineDoc/Exception.html" >SAException</A>. <A
href="../OnLineDoc/Exception_ErrPos.html">SAException::ErrPos</A>
method gets an error position in SQL statement. In
<STRONG>MySQL</STRONG>
server <A
href="../OnLineDoc/Exception_ErrPos.html">SAException::ErrPos</A> method
returns -1 because <STRONG>MySQL</STRONG>
does not support this function.</P>
<P>For more details see <A
href="../HowTo/errors.html">How To - Error handling</A>, <A
href="../OnLineDoc/Exception_Usage.html">SAException object</A>.</P>
<P> </P>
<H3><A
name="Special header files - Compile time">Special header files -
Compile time</A> </H3>
<P>The header files are in the <STRONG>include</STRONG> subdirectory of SQLAPI++
distributions:<BR><STRONG>#include <SQLAPI.h>
</STRONG>- main header, should be
used whenever SQLAPI++ is used.<BR><STRONG> #include <myAPI.h>
</STRONG>-
<STRONG>MySQL</STRONG> , should be included if direct MySQL C API calls are
required.</P>
<P>For more details see <A
href="../OnLineDoc/index.html#Instructions for Compiling and Linking Applications with SQLAPI++">Online Documentation - Instructions for
Compiling and Linking Applications with SQLAPI++</A> </P>
<P> </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></TBODY></TABLE></FONT>
</body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -