Edit C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\odbc\7.0.1\help\reference\thread.html
<?xml version="1.0" encoding="utf-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xml:lang="en" lang="en" xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> <meta http-equiv="Content-Style-Type" content="text/css" /> <!-- MOTW-DISABLED saved from url=(0014)about:internet --> <title>Threading</title> <link rel="StyleSheet" href="css/thread.css" type="text/css" media="all" /> <link rel="StyleSheet" href="css/webworks.css" type="text/css" media="all" /> <script type="text/javascript" language="JavaScript1.2" src="wwhdata/common/context.js"></script> <script type="text/javascript" language="JavaScript1.2" src="wwhdata/common/towwhdir.js"></script> <script type="text/javascript" language="JavaScript1.2" src="wwhdata/common/wwhpagef.js"></script> <script type="text/javascript" language="JavaScript1.2"> <!-- var WebWorksRootPath = ""; // --> </script> <script type="text/javascript" language="JavaScript1.2"> <!-- // Set reference to top level help frame // var WWHFrame = WWHGetWWHFrame("", true); // --> </script> <script type="text/javascript" language="JavaScript1.2" src="scripts/expand.js"></script> </head> <body class="" style="background-color: #FFFFEE;" onload="WWHUpdate();" onunload="WWHUnload();" onkeydown="WWHHandleKeyDown((document.all||document.getElementById||document.layers)?event:null);" onkeypress="WWHHandleKeyPress((document.all||document.getElementById||document.layers)?event:null);" onkeyup="WWHHandleKeyUp((document.all||document.getElementById||document.layers)?event:null);"> <br /> <div class="WebWorks_Breadcrumbs" style="text-align: left;">3 Threading</div> <hr align="left" /> <blockquote> <div class="chap_title_2_outer" style="margin-left: 0pt;"> <table border="0" cellspacing="0" cellpadding="0" summary=""> <tr style="vertical-align: baseline;"> <td> <div class="chap_title_2_inner" style="width: 39.6pt; white-space: nowrap;">3 </div> </td> <td width="100%"> <div class="chap_title_2_inner"><a name="106144">Threading</a></div> </td> </tr> </table> </div> <div class="Body"><a name="106145">The ODBC specification mandates that all drivers must be thread-safe, that is, drivers must </a>not fail when database requests are made on separate threads. It is a common misperception that issuing requests on separate threads always results in improved throughput. Because of network transport and database server limitations, some drivers serialize threaded requests to the server to ensure thread safety.</div> <div class="Body"><a name="106146">The ODBC 3.0 specification does not provide a method to find out how a driver services </a>threaded requests, although this information is useful to an application. All the DataDirect Connect Series <span class="forbody">for</span> <span class="APIbody">ODBC</span> drivers provide this information to the user through the SQLGetInfo information type 1028. </div> <div class="Body"><a name="106147">The result of calling SQLGetInfo with 1028 is a SQL_USMALLINT flag that denotes the </a>sessionā??s thread model. A return value of 0 denotes that the session is fully thread-enabled and that all requests use the threaded model. A return value of 1 denotes that the session is restricted at the connection level. Sessions of this type are fully thread-enabled when simultaneous threaded requests are made with statement handles that do not share the same connection handle. In this model, if multiple requests are made from the same connection, the first request received by the driver is processed immediately and all subsequent requests are serialized. A return value of 2 denotes that the session is thread-impaired and all requests are serialized by the driver. </div> <div class="Body"><a name="106148">Consider the following code fragment:</a></div> <div class="syntax_wide_first"><a name="106149">rc = SQLGetInfo (hdbc, 1028, &ThreadModel, NULL, NULL);</a></div> <div class="syntax_wide"><a name="106150"> </a></div> <div class="syntax_wide"><a name="106151">If (rc == SQL_SUCCESS) {</a></div> <div class="syntax_wide"><a name="106152"> </a> // driver is a DataDirect driver that can report threading information</div> <div class="syntax_wide"><a name="106154"> </a></div> <div class="syntax_wide"><a name="106155"> </a> if (ThreadModel == 0)</div> <div class="syntax_wide"><a name="106156"> </a> // driver is unconditionally thread-enabled; application can take advantage of threading</div> <div class="syntax_wide"><a name="106158"> </a></div> <div class="syntax_wide"><a name="106680"> </a> else if (ThreadModel == 1)</div> <div class="syntax_wide"><a name="106681"> </a> // driver is thread-enabled when thread requests are from different connections</div> <div class="syntax_wide"><a name="106162"> </a> // some applications can take advantage of threading</div> <div class="syntax_wide"><a name="106163"> </a></div> <div class="syntax_wide"><a name="106164"> </a> else if (ThreadModel == 2)</div> <div class="syntax_wide"><a name="106165"> </a> // driver is thread-impaired; application should only use threads if it reduces </div> <div class="syntax_wide"><a name="106704"> </a> // program complexity</div> <div class="syntax_wide"><a name="106168"> </a></div> <div class="syntax_wide"><a name="106169">}</a></div> <div class="syntax_wide"><a name="106170">else</a></div> <div class="syntax_wide"><a name="106171"> </a> // driver is guaranteed to be thread-safe; use threading at your own risk</div> <script type="text/javascript" language="JavaScript1.2"> <!-- // Clear related topics // WWHClearRelatedTopics(); document.writeln(WWHRelatedTopicsInlineHTML()); // --> </script> </blockquote> <script type="text/javascript" language="JavaScript1.2"> <!-- document.write(WWHRelatedTopicsDivTag() + WWHPopupDivTag() + WWHALinksDivTag()); // --> </script> </body> </html>
Ms-Dos/Windows
Unix
Write backup
jsp File Browser version 1.2 by
www.vonloesch.de