| Prev Class | Next Class | Frames | No Frames |
| Summary: Nested | Field | Method | Constr | Detail: Nested | Field | Method | Constr |
java.lang.Objectorg.hsqldb.jdbc.jdbcStatementpublic class jdbcStatementextends java.lang.Objectimplements StatementResultSet object per Statement
object can be open at the same time. Therefore, if the reading of one
ResultSet object is interleaved
with the reading of another, each must have been generated by
different Statement objects. All execution methods in the
Statement interface implicitly close a statment's current
ResultSet object if an open one exists.
<!-- end generic documentation-->
<!-- start release-specific documentation -->
int values that are defined only in the JDBC 2 or greater
version of the ResultSet interface. For this
reason these values are defined in jdbcResultSet.
In a JRE 1.1.x environment, calling JDBC 2 methods that take or return the
JDBC2-only ResultSet values can be achieved by referring
to them in parameter specifications and return value comparisons,
respectively, as follows:
jdbcResultSet.FETCH_FORWARD jdbcResultSet.TYPE_FORWARD_ONLY jdbcResultSet.TYPE_SCROLL_INSENSITIVE jdbcResultSet.CONCUR_READ_ONLY //etc.However, please note that code written to use HSQLDB JDBC 2 features under JDK 1.1.x will not be compatible for use with other JDBC 2 drivers. Please also note that this feature is offered solely as a convenience to developers who must work under JDK 1.1.x due to operating constraints, yet wish to use some of the more advanced features available under the JDBC 2 specification. (fredt@users)
jdbcConnection.createStatement, jdbcResultSetMethod Summary | |
void |
|
void |
|
void |
|
void |
|
void |
|
boolean |
|
boolean |
|
boolean |
|
boolean |
|
int[] |
|
ResultSet |
|
int |
|
int |
|
int |
|
int |
|
Connection |
|
int |
|
int |
|
ResultSet |
|
int |
|
int |
|
boolean |
|
boolean |
|
int |
|
ResultSet |
|
int |
|
int |
|
int |
|
int |
|
SQLWarning |
|
void |
|
void |
|
void |
|
void |
|
void |
|
void |
|
void |
|
public void addBatch(String sql)
throws SQLException<!-- start generic documentation --> Adds the given SQL command to the current list of commmands for thisStatementobject. The commands in this list can be executed as a batch by calling the methodexecuteBatch. NOTE: This method is optional. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Starting with 1.7.2, this feature is supported.
- Parameters:
sql- typically this is a static SQLINSERTorUPDATEstatement
- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcStatement)
- See Also:
executeBatch()
public void cancel()
throws SQLException<!-- start generic documentation --> Cancels thisStatementobject if both the DBMS and driver support aborting an SQL statement. This method can be used by one thread to cancel a statement that is being executed by another thread. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Including 1.7.2, HSQLDB does not support aborting a SQL statement; calls to this method are ignored.
public void clearBatch()
throws SQLException<!-- start generic documentation --> Empties thisStatementobject's current list of SQL commands. NOTE: This method is optional. <!-- start generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Starting with HSQLDB 1.7.2, this feature is supported.
- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcStatement)
- See Also:
addBatch(String)
public void clearWarnings()
throws SQLException<!-- start generic documentation --> Clears all the warnings reported on thisStatementobject. After a call to this method, the methodgetWarningswill returnnulluntil a new warning is reported for thisStatementobject. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Including HSQLDB 1.7.2,SQLWarningobjects are never produced for Statement Objects; calls to this method are ignored.
public void close()
throws SQLException<!-- start generic documentation --> Releases thisStatementobject's database and JDBC resources immediately instead of waiting for this to happen when it is automatically closed. It is generally good practice to release resources as soon as you are finished with them to avoid tying up database resources. Calling the methodcloseon aStatementobject that is already closed has no effect. Note: AStatementobject is automatically closed when it is garbage collected. When aStatementobject is closed, its currentResultSetobject, if one exists, is also closed. <!-- end generic documentation -->
public boolean execute(String sql)
throws SQLException<!-- start generic documentation --> Executes the given SQL statement, which may return multiple results. In some (uncommon) situations, a single SQL statement may return multiple result sets and/or update counts. Normally you can ignore this unless you are (1) executing a stored procedure that you know may return multiple results or (2) you are dynamically executing an unknown SQL string. Theexecutemethod executes an SQL statement and indicates the form of the first result. You must then use the methodsgetResultSetorgetUpdateCountto retrieve the result, andgetMoreResultsto move to any subsequent result(s). <!-- end generic documentation -->
- Parameters:
sql- any SQL statement
- Returns:
trueif the first result is aResultSetobject;falseif it is an update count or there are no results
- See Also:
getResultSet(),getUpdateCount(),getMoreResults
public boolean execute(String sql,
String[] columnNames)
throws SQLException<!-- start generic documentation --> Executes the given SQL statement, which may return multiple results, and signals the driver that the auto-generated keys indicated in the given array should be made available for retrieval. This array contains the names of the columns in the target table that contain the auto-generated keys that should be made available. The driver will ignore the array if the given SQL statement is not anINSERTstatement. In some (uncommon) situations, a single SQL statement may return multiple result sets and/or update counts. Normally you can ignore this unless you are (1) executing a stored procedure that you know may return multiple results or (2) you are dynamically executing an unknown SQL string. Theexecutemethod executes an SQL statement and indicates the form of the first result. You must then use the methodsgetResultSetorgetUpdateCountto retrieve the result, andgetMoreResultsto move to any subsequent result(s). <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature. Calling this method always throws anSQLException, stating that the function is not supported.
- Parameters:
sql- any SQL statementcolumnNames- an array of the names of the columns in the inserted row that should be made available for retrieval by a call to the methodgetGeneratedKeys
- Returns:
trueif the next result is aResultSetobject;falseif it is an update count or there are no more results
- Since:
- JDK 1.4, HSQLDB 1.7
- See Also:
getResultSet(),getUpdateCount(),getMoreResults,getGeneratedKeys()
public boolean execute(String sql,
int autoGeneratedKeys)
throws SQLException<!-- start generic documentation --> Executes the given SQL statement, which may return multiple results, and signals the driver that any auto-generated keys should be made available for retrieval. The driver will ignore this signal if the SQL statement is not anINSERTstatement. In some (uncommon) situations, a single SQL statement may return multiple result sets and/or update counts. Normally you can ignore this unless you are (1) executing a stored procedure that you know may return multiple results or (2) you are dynamically executing an unknown SQL string. Theexecutemethod executes an SQL statement and indicates the form of the first result. You must then use the methodsgetResultSetorgetUpdateCountto retrieve the result, andgetMoreResultsto move to any subsequent result(s). <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature. Calling this method always throws anSQLException, stating that the function is not supported.
- Parameters:
sql- any SQL statementautoGeneratedKeys- a constant indicating whether auto-generated keys should be made available for retrieval using the methodgetGeneratedKeys; one of the following constants:Statement.RETURN_GENERATED_KEYSorStatement.NO_GENERATED_KEYS
- Returns:
trueif the first result is aResultSetobject;falseif it is an update count or there are no results
- Since:
- JDK 1.4, HSQLDB 1.7
- See Also:
getResultSet(),getUpdateCount(),getMoreResults,getGeneratedKeys()
public boolean execute(String sql,
int[] columnIndexes)
throws SQLException<!-- start generic documentation --> Executes the given SQL statement, which may return multiple results, and signals the driver that the auto-generated keys indicated in the given array should be made available for retrieval. This array contains the indexes of the columns in the target table that contain the auto-generated keys that should be made available. The driver will ignore the array if the given SQL statement is not anINSERTstatement. Under some (uncommon) situations, a single SQL statement may return multiple result sets and/or update counts. Normally you can ignore this unless you are (1) executing a stored procedure that you know may return multiple results or (2) you are dynamically executing an unknown SQL string. Theexecutemethod executes an SQL statement and indicates the form of the first result. You must then use the methodsgetResultSetorgetUpdateCountto retrieve the result, andgetMoreResultsto move to any subsequent result(s). <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature. Calling this method always throws anSQLException, stating that the function is not supported.
- Parameters:
sql- any SQL statementcolumnIndexes- an array of the indexes of the columns in the inserted row that should be made available for retrieval by a call to the methodgetGeneratedKeys
- Returns:
trueif the first result is aResultSetobject;falseif it is an update count or there are no results
- Since:
- JDK 1.4, HSQLDB 1.7
- See Also:
getResultSet(),getUpdateCount(),getMoreResults
public int[] executeBatch()
throws SQLException<!-- start generic documentation --> Submits a batch of commands to the database for execution and if all commands execute successfully, returns an array of update counts. Theintelements of the array that is returned are ordered to correspond to the commands in the batch, which are ordered according to the order in which they were added to the batch. The elements in the array returned by the methodexecuteBatchmay be one of the following:A driver is not required to implement this method. The possible implementations and return values have been modified in the Java 2 SDK, Standard Edition, version 1.3 to accommodate the option of continuing to proccess commands in a batch update after a
- A number greater than or equal to zero -- indicates that the command was processed successfully and is an update count giving the number of rows in the database that were affected by the command's execution
- A value of
SUCCESS_NO_INFO-- indicates that the command was processed successfully but that the number of rows affected is unknown If one of the commands in a batch update fails to execute properly, this method throws aBatchUpdateException, and a JDBC driver may or may not continue to process the remaining commands in the batch. However, the driver's behavior must be consistent with a particular DBMS, either always continuing to process commands or never continuing to process commands. If the driver continues processing after a failure, the array returned by the methodBatchUpdateException.getUpdateCountswill contain as many elements as there are commands in the batch, and at least one of the elements will be the following:- A value of
EXECUTE_FAILED-- indicates that the command failed to execute successfully and occurs only if a driver continues to process commands after a command failsBatchUpdateExceptionobejct has been thrown. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Starting with HSQLDB 1.7.2, this feature is supported. HSQLDB stops execution of commands in a batch when one of the commands results in an exception. The size of the returned array equals the number of commands that were executed successfully. When the product is built under the JAVA1 target, an exception is never thrown and it is the responsibility of the client software to check the size of the returned update count array to determine if any batch items failed. To build and run under the JAVA2 target, JDK/JRE 1.3 or higher must be used.
- Returns:
- an array of update counts containing one element for each command in the batch. The elements of the array are ordered according to the order in which commands were added to the batch.
- Since:
- JDK 1.3 (JDK 1.1.x developers: read the new overview for jdbcStatement)
public ResultSet executeQuery(String sql)
throws SQLException<!-- start generic documentation --> Executes the given SQL statement, which returns a singleResultSetobject. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
This method should not be used for statements other than SELECT queries. Including 1.7.2, HSQLDB does not throw an exception when the statement is a DDL statement or an UPDATE or DELETE statement. This will certainly change in future version.
- Parameters:
sql- an SQL statement to be sent to the database, typically a static SQLSELECTstatement
- Returns:
- a
ResultSetobject that contains the data produced by the given query; nevernull
public int executeUpdate(String sql)
throws SQLException<!-- start generic documentation --> Executes the given SQL statement, which may be anINSERT,UPDATE, orDELETEstatement or an SQL statement that returns nothing, such as an SQL DDL statement. <!-- end generic documentation -->
- Parameters:
sql- an SQLINSERT,UPDATEorDELETEstatement or an SQL statement that returns nothing
- Returns:
- either the row count for
INSERT,UPDATEorDELETEstatements, or0for SQL statements that return nothing
public int executeUpdate(String sql,
String[] columnNames)
throws SQLException<!-- start generic documentation --> Executes the given SQL statement and signals the driver that the auto-generated keys indicated in the given array should be made available for retrieval. The driver will ignore the array if the SQL statement is not anINSERTstatement. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature. Calling this method always throws anSQLException, stating that the function is not supported.
- Parameters:
sql- an SQLINSERT,UPDATEorDELETEstatement or an SQL statement that returns nothingcolumnNames- an array of the names of the columns that should be returned from the inserted row
- Returns:
- either the row count for
INSERT,UPDATE, orDELETEstatements, or 0 for SQL statements that return nothing
- Since:
- JDK 1.4, HSQLDB 1.7
public int executeUpdate(String sql,
int autoGeneratedKeys)
throws SQLException<!-- start generic documentation --> Executes the given SQL statement and signals the driver with the given flag about whether the auto-generated keys produced by thisStatementobject should be made available for retrieval. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature. Calling this method always throws anSQLException, stating that the function is not supported.
- Parameters:
sql- must be an SQLINSERT,UPDATEorDELETEstatement or an SQL statement that returns nothingautoGeneratedKeys- a flag indicating whether auto-generated keys should be made available for retrieval; one of the following constants:Statement.RETURN_GENERATED_KEYSStatement.NO_GENERATED_KEYS
- Returns:
- either the row count for
INSERT,UPDATEorDELETEstatements, or0for SQL statements that return nothing
- Since:
- JDK 1.4, HSQLDB 1.7
public int executeUpdate(String sql,
int[] columnIndexes)
throws SQLException<!-- start generic documentation --> Executes the given SQL statement and signals the driver that the auto-generated keys indicated in the given array should be made available for retrieval. The driver will ignore the array if the SQL statement is not anINSERTstatement. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature. Calling this method always throws anSQLException, stating that the function is not supported.
- Parameters:
sql- an SQLINSERT,UPDATEorDELETEstatement or an SQL statement that returns nothing, such as an SQL DDL statementcolumnIndexes- an array of column indexes indicating the columns that should be returned from the inserted row
- Returns:
- either the row count for
INSERT,UPDATE, orDELETEstatements, or 0 for SQL statements that return nothing
- Since:
- JDK 1.4, HSQLDB 1.7
public Connection getConnection()
throws SQLException<!-- start generic documentation --> Retrieves theConnectionobject that produced thisStatementobject. <!-- end generic documentation -->
- Returns:
- the connection that produced this statement
- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcStatement)
public int getFetchDirection()
throws SQLException<!-- start generic documentation --> Retrieves the direction for fetching rows from database tables that is the default for result sets generated from thisStatementobject. If thisStatementobject has not set a fetch direction by calling the methodsetFetchDirection, the return value is implementation-specific. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Including 1.7.2, HSQLDB always returns FETCH_FORWARD.
- Returns:
- the default fetch direction for result sets generated from this
Statementobject
- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcStatement)
- See Also:
setFetchDirection(int)
public int getFetchSize()
throws SQLException<!-- start generic documentation --> Retrieves the number of result set rows that is the default fetch size forResultSetobjects generated from thisStatementobject. If thisStatementobject has not set a fetch size by calling the methodsetFetchSize, the return value is implementation-specific. <!-- end generic documentation --> <!-- start release-specific documentation -->HSQLDB-Specific Information Including 1.7.2, this method always returns 0. HSQLDB fetches each result completely as part of executing its statement<!-- end release-specific documentation -->
- Returns:
- the default fetch size for result sets generated from this
Statementobject
- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcStatement)
- See Also:
setFetchSize(int)
public ResultSet getGeneratedKeys()
throws SQLException<!-- start generic documentation --> Retrieves any auto-generated keys created as a result of executing thisStatementobject. If thisStatementobject did not generate any keys, an emptyResultSetobject is returned. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature. Calling this method always throws anSQLException, stating that the function is not supported.
- Returns:
- a
ResultSetobject containing the auto-generated key(s) generated by the execution of thisStatementobject
- Since:
- JDK 1.4, HSQLDB 1.7
public int getMaxFieldSize()
throws SQLException<!-- start generic documentation --> Retrieves the maximum number of bytes that can be returned for character and binary column values in aResultSetobject produced by thisStatementobject. This limit applies only toBINARY,VARBINARY,LONGVARBINARY,CHAR,VARCHAR, andLONGVARCHARcolumns. If the limit is exceeded, the excess data is silently discarded. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Including 1.7.2, HSQLDB always returns zero, meaning there is no limit.
- Returns:
- the current column size limit for columns storing character and binary values; zero means there is no limit
- See Also:
setMaxFieldSize(int)
public int getMaxRows()
throws SQLException<!-- start generic documentation --> Retrieves the maximum number of rows that aResultSetobject produced by thisStatementobject can contain. If this limit is exceeded, the excess rows are silently dropped. <!-- start generic documentation -->
- Returns:
- the current maximum number of rows for a
ResultSetobject produced by thisStatementobject; zero means there is no limit
- See Also:
setMaxRows(int)
public boolean getMoreResults()
throws SQLException<!-- start generic documentation --> Moves to thisStatementobject's next result, returnstrueif it is aResultSetobject, and implicitly closes any currentResultSetobject(s) obtained with the methodgetResultSet. There are no more results when the following is true:<!-- end generic documentation -->(!getMoreResults() && (getUpdateCount() == -1)
- Returns:
trueif the next result is aResultSetobject;falseif it is an update count or there are no more results
- See Also:
execute
public boolean getMoreResults(int current)
throws SQLException<!-- start generic documentation --> Moves to thisStatementobject's next result, deals with any currentResultSetobject(s) according to the instructions specified by the given flag, and returnstrueif the next result is aResultSetobject. There are no more results when the following is true:<!-- end generic documentation --> <!-- start release-specific documentation -->(!getMoreResults() && (getUpdateCount() == -1)<!-- end release-specific documentation -->HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature. Calling this method always throws anSQLException, stating that the function is not supported.
- Parameters:
current- one of the followingStatementconstants indicating what should happen to currentResultSetobjects obtained using the methodgetResultSetCLOSE_CURRENT_RESULT,KEEP_CURRENT_RESULT, orCLOSE_ALL_RESULTS
- Returns:
trueif the next result is aResultSetobject;falseif it is an update count or there are no more results
- Since:
- JDK 1.4, HSQLDB 1.7
- See Also:
execute
public int getQueryTimeout()
throws SQLException<!-- start generic documentation --> Retrieves the number of seconds the driver will wait for aStatementobject to execute. If the limit is exceeded, anSQLExceptionis thrown. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Including 1.7.2, HSQLDB always returns zero, meaning there is no limit.
- Returns:
- the current query timeout limit in seconds; zero means there is no limit
- See Also:
setQueryTimeout(int)
public ResultSet getResultSet()
throws SQLException<!-- start generic documentation --> Retrieves the current result as aResultSetobject. This method should be called only once per result. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Without an interceding call to executeXXX, each invocation of this method will produce a new, initialized ResultSet instance referring to the current result, if any.
- Returns:
- the current result as a
ResultSetobject ornullif the result is an update count or there are no more results
- See Also:
execute
public int getResultSetConcurrency()
throws SQLException<!-- start generic documentation --> Retrieves the result set concurrency forResultSetobjects generated by thisStatementobject. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Including 1.7.2, HSQLDB supports onlyCONCUR_READ_ONLYconcurrency.
- Returns:
- either
ResultSet.CONCUR_READ_ONLYorResultSet.CONCUR_UPDATABLE(not supported)
- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcStatement)
public int getResultSetHoldability()
throws SQLException<!-- start generic documentation --> Retrieves the result set holdability forResultSetobjects generated by thisStatementobject. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Starting with 1.7.2, this method returns HOLD_CURSORS_OVER_COMMIT
- Returns:
- either
ResultSet.HOLD_CURSORS_OVER_COMMITorResultSet.CLOSE_CURSORS_AT_COMMIT
- Since:
- JDK 1.4, HSQLDB 1.7
public int getResultSetType()
throws SQLException<!-- start generic documentation --> Retrieves the result set type forResultSetobjects generated by thisStatementobject. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
HSQLDB 1.7.0 and later versions supportTYPE_FORWARD_ONLYandTYPE_SCROLL_INSENSITIVE.
- Returns:
- one of
ResultSet.TYPE_FORWARD_ONLY,ResultSet.TYPE_SCROLL_INSENSITIVE, orResultSet.TYPE_SCROLL_SENSITIVE(not supported) Note: Up to and including 1.7.1, HSQLDB never returnsTYPE_SCROLL_SENSITIVE
- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcStatement)
public int getUpdateCount()
throws SQLException<!-- start generic documentation --> Retrieves the current result as an update count; if the result is aResultSetobject or there are no more results, -1 is returned. This method should be called only once per result. <!-- end generic documentation -->
- Returns:
- the current result as an update count; -1 if the current result is a
ResultSetobject or there are no more results
- See Also:
execute
public SQLWarning getWarnings()
throws SQLException<!-- start generic documentation --> Retrieves the first warning reported by calls on thisStatementobject. SubsequentStatementobject warnings will be chained to thisSQLWarningobject. The warning chain is automatically cleared each time a statement is (re)executed. This method may not be called on a closedStatementobject; doing so will cause anSQLExceptionto be thrown. Note: If you are processing aResultSetobject, any warnings associated with reads on thatResultSetobject will be chained on it rather than on theStatementobject that produced it. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Including 1.7.2, HSQLDB never produces Statement warnings; this method always returns null.
- Returns:
- the first
SQLWarningobject ornullif there are no warnings
public void setCursorName(String name)
throws SQLException<!-- start generic documentation --> Sets the SQL cursor name to the givenString, which will be used by subsequentStatementobjectexecutemethods. This name can then be used in SQL positioned update or delete statements to identify the current row in theResultSetobject generated by this statement. If the database does not support positioned update/delete, this method is a noop. To insure that a cursor has the proper isolation level to support updates, the cursor'sSELECTstatement should have the formSELECT FOR UPDATE. IfFOR UPDATEis not present, positioned updates may fail. Note: By definition, the execution of positioned updates and deletes must be done by a differentStatementobject than the one that generated theResultSetobject being used for positioning. Also, cursor names must be unique within a connection. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Including 1.7.2, HSQLDB does not support named cursors, updateable results or table locking viaSELECT FOR UPDATE; calls to this method are ignored.
- Parameters:
name- the new cursor name, which must be unique within a connection
public void setEscapeProcessing(boolean enable)
throws SQLException<!-- start generic documentation --> Sets escape processing on or off. If escape scanning is on (the default), the driver will do escape substitution before sending the SQL statement to the database. Note: Since prepared statements have usually been parsed prior to making this call, disabling escape processing forPreparedStatementsobjects will have no effect. <!-- end generic documentation -->
- Parameters:
enable-trueto enable escape processing;falseto disable it
public void setFetchDirection(int direction)
throws SQLException<!-- start generic documentation --> Gives the driver a hint as to the direction in which rows will be processed inResultSetobjects created using thisStatementobject. The default value isResultSet.FETCH_FORWARD. Note that this method sets the default fetch direction for result sets generated by thisStatementobject. Each result set has its own methods for getting and setting its own fetch direction. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Including 1.7.2, HSQLDB supports onlyFETCH_FORWARD. Setting any other value will throw anSQLExceptionstating that the operation is not supported.
- Parameters:
direction- the initial direction for processing rows
- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcStatement)
- See Also:
getFetchDirection()
public void setFetchSize(int rows)
throws SQLException<!-- start generic documentation --> Gives the JDBC driver a hint as to the number of rows that should be fetched from the database when more rows are needed. The number of rows specified affects only result sets created using this statement. If the value specified is zero, then the hint is ignored. The default value is zero. <!-- start generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Including 1.7.2, calls to this method are ignored; HSQLDB fetches each result completely as part of executing its statement.
- Parameters:
rows- the number of rows to fetch
- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcStatement)
- See Also:
getFetchSize()
public void setMaxFieldSize(int max)
throws SQLException<!-- start generic documentation --> Sets the limit for the maximum number of bytes in aResultSetcolumn storing character or binary values to the given number of bytes. This limit applies only toBINARY,VARBINARY,LONGVARBINARY,CHAR,VARCHAR, andLONGVARCHARfields. If the limit is exceeded, the excess data is silently discarded. For maximum portability, use values greater than 256. <!-- emd generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Including 1.7.2, calls to this method are simply ignored; HSQLDB always stores the full number of bytes when dealing with any of the field types mentioned above. These types all have an absolute maximum element upper bound determined by the Java array index limit java.lang.Integer.MAX_VALUE. For XXXBINARY types, this translates to Integer.MAX_VALUE bytes. For XXXCHAR types, this translates to 2 * Integer.MAX_VALUE bytes (2 bytes / character)
- Parameters:
max- the new column size limit in bytes; zero means there is no limit
- See Also:
getMaxFieldSize()
public void setMaxRows(int max)
throws SQLException<!-- start generic documentation --> Sets the limit for the maximum number of rows that anyResultSetobject can contain to the given number. If the limit is exceeded, the excess rows are silently dropped. <!-- end generic documentation -->
- Parameters:
max- the new max rows limit; zero means there is no limit
- See Also:
getMaxRows()
public void setQueryTimeout(int seconds)
throws SQLException<!-- start generic documentation --> Sets the number of seconds the driver will wait for aStatementobject to execute to the given number of seconds. If the limit is exceeded, anSQLExceptionis thrown. <!-- end generic documentation --> <!-- start release-specific documentation --><!-- end release-specific documentation -->HSQLDB-Specific Information:
Including 1.7.2, calls to this method are ignored; HSQLDB waits an unlimited amount of time for statement execution requests to return.
- Parameters:
seconds- the new query timeout limit in seconds; zero means there is no limit
- See Also:
getQueryTimeout()