<html> <head> <title>Service Statement</title> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <link rel="stylesheet" type="text/css" href="../../../../idl.css"> </head> <body> <div id="adc-idlref"> <a name="_top_"> </a><table class="navimain" border="0" cellpadding="3"> <tr> <td class="navimain"><a href="../module-ix.html" class="navimain">Overview</a></td> <td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td> <td class="navimain"><a href="Statement-xref.html" class="navimain">Use</a></td> <td class="navimain"><a href="http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Creating_Statements" class="navimain">Devguide</a></td> <td class="navimain"><a href="../../../../index-files/index-1.html" class="navimain">Index</a></td> </tr> </table> <table class="navisub" border="0" cellpadding="0"> <tr> <td class="navisub">Included Services</td> <td class="navisub"><a href="#ExportedInterfaces" class="navisub">Exported Interfaces</a></td> <td class="navisub"><a href="#PropertiesSummary" class="navisub">Properties' Summary</a></td> <td class="navisub"><a href="#PropertiesDetails" class="navisub">Properties' Details</a></td> </tr> </table> <hr> <table border="0" width="100%" cellpadding="5" cellspacing="3" class="title-table" style="margin-bottom:6pt;"> <tr> <td><p class="namechain"><a href="../../../../module-ix.html" class="namechain">::</a> <a href="../../../module-ix.html" class="namechain">com</a> :: <a href="../../module-ix.html" class="namechain">sun</a> :: <a href="../module-ix.html" class="namechain">star</a> :: <a href="module-ix.html" class="namechain">sdbc</a> :: </p> </td> </tr> <tr> <td class="title">service Statement</td> </tr> <tr> <td><dl> <dt><b>Description</b></dt> <dd>is used for executing a static SQL statement and obtaining the results produced by it. </dd> <dd><p> Only one ResultSet per Statement can be open at any point in time. Therefore, if the reading of one ResultSet is interleaved with the reading of another, each must have been generated by different Statements. All statement <code>execute</code> methods implicitly close a statement's current ResultSet if an open one exists. </p> </dd> </dl> <a name="devmanual"> </a><dl> <dt><b>Developers Guide</b></dt> <dd><a href="http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Creating_Statements">Database - Creating Statements</a></dd> </dl> </td> </tr> </table> <hr> <a name="ExportedInterfaces"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle"> <tr> <td class="subtitle" colspan="2">Exported Interfaces</td> </tr> <tr> <td class="imsum_left">::com::sun::star::<a href="../lang/module-ix.html">lang</a>::<a href="../lang/XComponent.html">XComponent</a></td> <td class="imsum_right"><dl> <dt><b>Usage Restrictions</b></dt> <dd><i>optional</i></dd> <dt><b>Description</b></dt> <dd>optional for implementation, controls the releasing of resources and the notification of registered listeners. </dd> </dl> </td> </tr> <tr> <td class="imsum_left"><a href="XCloseable.html">XCloseable</a></td> <td class="imsum_right"><dl> <dt><b>Description</b></dt> <dd>freeing all resources of a statement. A related resultset will be freed as well. </dd> </dl> </td> </tr> <tr> <td class="imsum_left">::com::sun::star::<a href="../beans/module-ix.html">beans</a>::<a href="../beans/XPropertySet.html">XPropertySet</a></td> <td class="imsum_right"><dl> <dt>(referenced entity's summary:)</dt> <dd>provides information about and access to the properties from an implementation. </dd> </dl> </td> </tr> <tr> <td class="imsum_left">::com::sun::star::<a href="../util/module-ix.html">util</a>::<a href="../util/XCancellable.html">XCancellable</a></td> <td class="imsum_right"><dl> <dt><b>Usage Restrictions</b></dt> <dd><i>optional</i></dd> <dt><b>Description</b></dt> <dd>could be used for cancelling the execution of SQL statements if both the DBMS and the driver support aborting an SQL statement. The implementation is optional. </dd> </dl> </td> </tr> <tr> <td class="imsum_left"><a href="XStatement.html">XStatement</a></td> <td class="imsum_right"><dl> <dt><b>Description</b></dt> <dd>is the interface for executing SQL commands. </dd> </dl> </td> </tr> <tr> <td class="imsum_left"><a href="XBatchExecution.html">XBatchExecution</a></td> <td class="imsum_right"><dl> <dt><b>Usage Restrictions</b></dt> <dd><i>optional</i></dd> <dt><b>Description</b></dt> <dd>provides the ability of batch execution. This interface is optional for execution. </dd> <dd><p> A driver implementing batch execution must return <b>true</b> for <a href="XDatabaseMetaData.html">XDatabaseMetaData</a>::<a href="XDatabaseMetaData.html#supportsBatchUpdates">supportsBatchUpdates()</a> </p> </dd> </dl> </td> </tr> <tr> <td class="imsum_left"><a href="XWarningsSupplier.html">XWarningsSupplier</a></td> <td class="imsum_right"><dl> <dt><b>Description</b></dt> <dd>controls the chaining of warnings, which may occur on every call to the connected database. Chained warnings from previous calls will be cleared before processing a new call. </dd> </dl> </td> </tr> <tr> <td class="imsum_left"><a href="XMultipleResults.html">XMultipleResults</a></td> <td class="imsum_right"><dl> <dt><b>Usage Restrictions</b></dt> <dd><i>optional</i></dd> <dt><b>Description</b></dt> <dd>covers the handling of multiple results after executing an SQL command. The implementation is optional. </dd> </dl> </td> </tr> </table> <a name="PropertiesSummary"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle"> <tr> <td class="subtitle" colspan="2">Properties' Summary</td> </tr> <tr> <td class="imsum_left">long<br> <a href="#QueryTimeOut">QueryTimeOut</a></td> <td class="imsum_right">retrieves the number of seconds the driver will wait for a Statement to execute. If the limit is exceeded, a SQLException is thrown. There is no limitation, if set to zero. </td> </tr> <tr> <td class="imsum_left">long<br> <a href="#MaxFieldSize">MaxFieldSize</a></td> <td class="imsum_right">returns the maximum number of bytes allowed for any column value. </td> </tr> <tr> <td class="imsum_left">long<br> <a href="#MaxRows">MaxRows</a></td> <td class="imsum_right">retrieves the maximum number of rows that a ResultSet can contain. If the limit is exceeded, the excess rows are silently dropped. <br/> There is no limitation, if set to zero. </td> </tr> <tr> <td class="imsum_left">string<br> <a href="#CursorName">CursorName</a></td> <td class="imsum_right">defines the SQL cursor name that will be used by subsequent Statement <code>execute</code> methods. </td> </tr> <tr> <td class="imsum_left">long<br> <a href="#ResultSetConcurrency">ResultSetConcurrency</a></td> <td class="imsum_right">retrieves the result set concurrency. </td> </tr> <tr> <td class="imsum_left">long<br> <a href="#ResultSetType">ResultSetType</a></td> <td class="imsum_right">determine the result set type. </td> </tr> <tr> <td class="imsum_left">long<br> <a href="#FetchDirection">FetchDirection</a></td> <td class="imsum_right">retrieves the direction for fetching rows from database tables that is the default for result sets generated from this <code>Statement</code> object. <br/> If this <code>Statement</code> object has not set a fetch direction, the return value is implementation-specific. </td> </tr> <tr> <td class="imsum_left">long<br> <a href="#FetchSize">FetchSize</a></td> <td class="imsum_right">retrieves the number of result set rows that is the default fetch size for result sets generated from this <code>Statement</code> object. <br/> If this <code>Statement</code> object has not set a fetch size, the return value is implementation-specific. </td> </tr> <tr> <td class="imsum_left">boolean<br> <a href="#EscapeProcessing">EscapeProcessing</a></td> <td class="imsum_right">returns if escape processing is on or off. If escape scanning is on (the default), the driver will do escape substitution before sending the SQL to the database. </td> </tr> </table> <a name="PropertiesDetails"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle"> <tr> <td class="subtitle">Properties' Details</td> </tr> <tr> <td class="imdetail"><a name="QueryTimeOut" class="membertitle">QueryTimeOut</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center"> <tr> <td>long <b>QueryTimeOut</b>;<hr> <dl> <dt><b>Description</b></dt> <dd>retrieves the number of seconds the driver will wait for a Statement to execute. If the limit is exceeded, a SQLException is thrown. There is no limitation, if set to zero. </dd> </dl> </td> </tr> </table> </td> </tr> <tr> <td class="imdetail"><a name="MaxFieldSize" class="membertitle">MaxFieldSize</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center"> <tr> <td>long <b>MaxFieldSize</b>;<hr> <dl> <dt><b>Description</b></dt> <dd>returns the maximum number of bytes allowed for any column value. </dd> <dd><p> This limit is the maximum number of bytes that can be returned for any column value. The limit applies only to <a href="DataType.html">DataType</a>::<a href="DataType.html#BINARY">BINARY</a> , <a href="DataType.html">DataType</a>::<a href="DataType.html#VARBINARY">VARBINARY</a> , <a href="DataType.html">DataType</a>::<a href="DataType.html#LONGVARBINARY">LONGVARBINARY</a> , <a href="DataType.html">DataType</a>::<a href="DataType.html#CHAR">CHAR</a> , <a href="DataType.html">DataType</a>::<a href="DataType.html#VARCHAR">VARCHAR</a> , and <a href="DataType.html">DataType</a>::<a href="DataType.html#LONGVARCHAR">LONGVARCHAR</a> columns. If the limit is exceeded, the excess data is silently discarded. <br/> There is no limitation, if set to zero. </p> </dd> </dl> </td> </tr> </table> </td> </tr> <tr> <td class="imdetail"><a name="MaxRows" class="membertitle">MaxRows</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center"> <tr> <td>long <b>MaxRows</b>;<hr> <dl> <dt><b>Description</b></dt> <dd>retrieves the maximum number of rows that a ResultSet can contain. If the limit is exceeded, the excess rows are silently dropped. <br/> There is no limitation, if set to zero. </dd> </dl> </td> </tr> </table> </td> </tr> <tr> <td class="imdetail"><a name="CursorName" class="membertitle">CursorName</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center"> <tr> <td>string <b>CursorName</b>;<hr> <dl> <dt><b>Description</b></dt> <dd>defines the SQL cursor name that will be used by subsequent Statement <code>execute</code> methods. </dd> <dd><p> This name can then be used in SQL positioned update/delete statements to identify the current row in the ResultSet generated by this statement. If the database does not support positioned update/delete, this property is a noop. To insure that a cursor has the proper isolation level to support updates, the cursor's SELECT statement should be of the form 'select for update ...'. If the 'for update' phrase is omitted, positioned updates may fail. </p> <p> <b> Note: </b> By definition, positioned update/delete execution must be done by a different Statement than the one which generated the ResultSet being used for positioning. Also, cursor names must be unique within a connection. </p> </dd> </dl> </td> </tr> </table> </td> </tr> <tr> <td class="imdetail"><a name="ResultSetConcurrency" class="membertitle">ResultSetConcurrency</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center"> <tr> <td>long <b>ResultSetConcurrency</b>;<hr> <dl> <dt><b>Description</b></dt> <dd>retrieves the result set concurrency. </dd> <dt><b>See also</b></dt> <dd><a href="ResultSetConcurrency.html">ResultSetConcurrency</a></dd> </dl> </td> </tr> </table> </td> </tr> <tr> <td class="imdetail"><a name="ResultSetType" class="membertitle">ResultSetType</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center"> <tr> <td>long <b>ResultSetType</b>;<hr> <dl> <dt><b>Description</b></dt> <dd>determine the result set type. </dd> <dt><b>See also</b></dt> <dd><a href="ResultSetType.html">ResultSetType</a></dd> </dl> </td> </tr> </table> </td> </tr> <tr> <td class="imdetail"><a name="FetchDirection" class="membertitle">FetchDirection</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center"> <tr> <td>long <b>FetchDirection</b>;<hr> <dl> <dt><b>Description</b></dt> <dd>retrieves the direction for fetching rows from database tables that is the default for result sets generated from this <code>Statement</code> object. <br/> If this <code>Statement</code> object has not set a fetch direction, the return value is implementation-specific. </dd> </dl> </td> </tr> </table> </td> </tr> <tr> <td class="imdetail"><a name="FetchSize" class="membertitle">FetchSize</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center"> <tr> <td>long <b>FetchSize</b>;<hr> <dl> <dt><b>Description</b></dt> <dd>retrieves the number of result set rows that is the default fetch size for result sets generated from this <code>Statement</code> object. <br/> If this <code>Statement</code> object has not set a fetch size, the return value is implementation-specific. </dd> </dl> </td> </tr> </table> </td> </tr> <tr> <td class="imdetail"><a name="EscapeProcessing" class="membertitle">EscapeProcessing</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center"> <tr> <td>boolean <b>EscapeProcessing</b>;<hr> <dl> <dt><b>Description</b></dt> <dd>returns if escape processing is on or off. If escape scanning is on (the default), the driver will do escape substitution before sending the SQL to the database. </dd> </dl> </td> </tr> </table> </td> </tr> </table> <br> <a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright © 2008 Sun Microsystems, Inc.</p> </div> <!-- id="adc-idlref" --> </body> </html>