亚洲欧美第一页_禁久久精品乱码_粉嫩av一区二区三区免费野_久草精品视频

? 歡迎來到蟲蟲下載站! | ?? 資源下載 ?? 資源專輯 ?? 關于我們
? 蟲蟲下載站

?? mysql.html

?? 通用的數據庫中間庫
?? HTML
?? 第 1 頁 / 共 2 頁
字號:
            types correspond with servers original data types:</P>
            <P><EM>SA_dtLongBinary</EM> &lt;= &gt; BLOB<BR><EM>SA_dtLongChar</EM> &lt;= &gt; TEXT<BR 
            ><EM>SA_dtBLob</EM> = &gt; 
            BLOB<BR><EM>SA_dtCLob 
            </EM>=&gt; 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>&nbsp;</P>
            
            <H3><A 
            name="Returning output parameters">Returning output 
            parameters</A>  </H3>
            <p><STRONG> MySQL</STRONG> 
               server does not support stored procedures.</p>
            <P>&nbsp;</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>&nbsp;</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>&nbsp; </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: 
                        &quot;use&quot; to force SQLAPI++ to call 
                        <EM>mysql_use_result()</EM> function, &quot;store&quot; 
                        to force SQLAPI++ to call <EM>mysql_store_result()</EM>    
                            function.<BR>  Default value: &quot;use&quot;.
					</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>&nbsp;</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 
                &lt;myAPI.h&gt;</STRONG></P> </STRONG></TD></TR>
			</TABLE> </P>
            <P>To get more information about DBMS API 
            functions see this DBMS specific documentation.&nbsp; </P>
            <P>For more details see <A 
            href="../OnLineDoc/Connection_NativeAPI.html">SAConnection::NativeAPI</A>.</P>
            <P>&nbsp;</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 
                        &lt;myAPI.h&gt;</FONT> </STRONG></P>
                        <P>saConnectionHandles *pResult = 
                        con.NativeHandles</FONT>();<BR>myConnectionHandles *p_myCH 
                        =<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
                        (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.&nbsp; 
            </P>
            <P>For more details see <A 
            href="../OnLineDoc/Connection_NativeHandles.html">SAConnection::NativeHandles</A>.</P>
            <P>&nbsp;</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 
                        &lt;myAPI.h&gt;</FONT> </STRONG></P>
                        <P>saCommandHandles *pResult = 
                        cmd.NativeHandles</FONT>();<BR>myCommandHandles *p_myCH 
                        =<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
                        (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.&nbsp; 
            </P>
            <P>For more details see <A 
            href="../OnLineDoc/Command_NativeHandles.html">SACommand::NativeHandles</A>.</P>
            <P>&nbsp;</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>&nbsp;</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 &lt;SQLAPI.h&gt; 
            </STRONG>- main header, should be 
            used whenever SQLAPI++ is used.<BR><STRONG> #include &lt;myAPI.h&gt; 
            </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>&nbsp;</P>
            <P>&nbsp;</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 + -
亚洲欧美第一页_禁久久精品乱码_粉嫩av一区二区三区免费野_久草精品视频
91精品国产综合久久精品| 国产在线精品视频| 国产精品麻豆99久久久久久| 精品不卡在线视频| 精品日韩一区二区| 日韩欧美aaaaaa| 欧美大片在线观看| 精品对白一区国产伦| 欧美大肚乱孕交hd孕妇| 日韩午夜精品视频| 日韩网站在线看片你懂的| 日韩一级完整毛片| 久久婷婷一区二区三区| 国产精品少妇自拍| 一区二区高清在线| 视频一区二区三区在线| 久草这里只有精品视频| 国产精品综合在线视频| 99久久精品一区二区| 在线观看av一区二区| 欧美日本一道本| 精品国产91乱码一区二区三区| 久久久久免费观看| 国产色综合久久| 日韩精品亚洲专区| 亚洲成人三级小说| 久久精品av麻豆的观看方式| 九九九久久久精品| 国产不卡高清在线观看视频| 成人18视频在线播放| 欧美亚洲另类激情小说| 欧美电影免费观看完整版| 欧美激情在线看| 欧美精品xxxxbbbb| 久久久久久免费| 亚洲精品国产无天堂网2021 | 一区视频在线播放| 一区二区在线观看av| 久久国产视频网| 91美女精品福利| 欧美成人a视频| 亚洲欧洲美洲综合色网| 久久99国产乱子伦精品免费| 91啪亚洲精品| 久久久久99精品国产片| 亚瑟在线精品视频| 成人丝袜18视频在线观看| 欧美男生操女生| 中文字幕 久热精品 视频在线| 亚洲成在线观看| 99国产精品国产精品久久| 精品国产一区二区三区久久影院 | 久久影院午夜论| 亚洲国产欧美在线| 成人av网站免费| 久久久电影一区二区三区| 免费成人av资源网| 欧美性一二三区| 亚洲视频在线观看三级| 国产精品一卡二卡| 日韩三级精品电影久久久| 亚洲一区精品在线| 色拍拍在线精品视频8848| 日本一区二区三区久久久久久久久不| 首页亚洲欧美制服丝腿| 在线视频国内自拍亚洲视频| 中文字幕一区二区5566日韩| 国产在线一区二区| 日韩精品一区二区三区在线观看| 午夜激情一区二区三区| 欧美丝袜第三区| 亚洲成人一区二区| 欧美日韩一区二区三区高清| 亚洲图片欧美视频| 91高清视频在线| 亚洲伊人伊色伊影伊综合网| 色欧美乱欧美15图片| 亚洲尤物视频在线| 欧美日韩二区三区| 丝瓜av网站精品一区二区| 91精品国产综合久久久久久| 免费日本视频一区| 日韩欧美亚洲另类制服综合在线| 日本午夜精品一区二区三区电影| 欧美日韩国产高清一区| 日韩影院精彩在线| 欧美tk—视频vk| 国内精品国产成人国产三级粉色| 精品国产网站在线观看| 国产精品系列在线观看| 亚洲国产精品精华液2区45| 不卡av电影在线播放| 亚洲三级在线观看| 欧美日韩精品一区二区三区四区 | 一区二区三区四区av| 在线观看视频一区二区| 日一区二区三区| 久久亚洲免费视频| 99久久婷婷国产综合精品电影| 亚洲制服欧美中文字幕中文字幕| 欧美日韩亚洲国产综合| 国产一区二区网址| 国产精品毛片a∨一区二区三区| 欧美在线你懂得| 国产在线精品一区二区不卡了| 国产精品久久久久久久久久久免费看 | 国产午夜精品美女毛片视频| 99riav一区二区三区| 午夜视频一区在线观看| 欧美精品一区二区三区在线 | 麻豆精品新av中文字幕| 国产欧美日韩亚州综合 | 一区二区三区欧美| 欧美大片免费久久精品三p| 99综合电影在线视频| 日韩在线a电影| 国产精品国产三级国产有无不卡 | 这里只有精品99re| 国产美女在线观看一区| 天天综合色天天综合色h| 国产欧美一区二区三区网站| 欧美福利电影网| av影院午夜一区| 久久国产福利国产秒拍| 亚洲午夜影视影院在线观看| 亚洲国产精华液网站w| 69堂国产成人免费视频| 成人黄色av网站在线| 激情小说欧美图片| 亚洲va韩国va欧美va| 国产欧美精品在线观看| 日韩欧美一级二级| 欧美日韩三级在线| 一本久久a久久精品亚洲| 国产成a人亚洲精| 久久精品国产99国产| 日韩成人精品在线观看| 亚洲午夜私人影院| 亚洲精品视频免费观看| 中文av一区特黄| 国产午夜精品久久| 久久综合av免费| 日韩美女主播在线视频一区二区三区| 91国产成人在线| 色嗨嗨av一区二区三区| 成人app网站| 9色porny自拍视频一区二区| 成人中文字幕电影| 高清成人在线观看| 国产成人午夜精品影院观看视频 | 99riav久久精品riav| 成人黄色电影在线| 99久久久国产精品免费蜜臀| www.亚洲人| 91玉足脚交白嫩脚丫在线播放| 成人免费看视频| 成人午夜视频免费看| 国产a精品视频| 99久久夜色精品国产网站| 99久久99久久精品免费观看| 99精品一区二区三区| 91国产成人在线| 欧美久久久久久蜜桃| 欧美一区国产二区| 精品国产乱码久久久久久1区2区| 26uuu亚洲婷婷狠狠天堂| 久久久久久久久久电影| 国产精品久久久久精k8| 亚洲精品免费在线| 午夜不卡av免费| 久久99久久久久| 精品国产乱码久久久久久蜜臀 | 裸体歌舞表演一区二区| 久久精品国产成人一区二区三区 | 国产精品美女久久久久久久| 国产精品久久久久久久蜜臀| 成人动漫一区二区| 在线日韩av片| 欧美一区二区在线不卡| 国产色产综合产在线视频| 国产精品欧美一区喷水| 亚洲福中文字幕伊人影院| 久久黄色级2电影| www.亚洲精品| 欧美久久久影院| 中文字幕+乱码+中文字幕一区| 亚洲成人三级小说| 国产成人综合网站| 欧美色图12p| 国产欧美日本一区视频| 亚洲一卡二卡三卡四卡五卡| 国内国产精品久久| 在线观看欧美精品| ww亚洲ww在线观看国产| 夜夜亚洲天天久久| 国产一区91精品张津瑜| 欧美性大战久久久| 国产亚洲精品7777| 免费欧美在线视频| 日本精品视频一区二区三区|