| java.lang.Object
 org.hsqldb.jdbc.jdbcStatement
All known Subclasses: org.hsqldb.jdbc.jdbcPreparedStatement,
| jdbcStatement | | public class jdbcStatement implements Statement(Code) | |
The object used for executing a static SQL statement
and returning the results it produces.
By default, only one ResultSet 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.
HSQLDB-Specific Information:
JRE 1.1.x Notes:
In general, JDBC 2 support requires Java 1.2 and above, and JDBC3 requires
Java 1.4 and above. In HSQLDB, support for methods introduced in different
versions of JDBC depends on the JDK version used for compiling and building
HSQLDB.
Since 1.7.0, all JDBC 2 methods can be called while executing under the
version 1.1.x
Java Runtime EnvironmentTM.
However, in addition to this technique requiring explicit casts to the
org.hsqldb.jdbcXXX classes, some of these method calls require
int values that are defined only in the JDBC 2 or greater
version of the
java.sql.ResultSet ResultSet interface. For this
reason these values are defined in
jdbcResultSet 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)
(boucherb@users)
author:
boucherb@users
author:
fredt@user
version:
1.8.0
See Also: jdbcConnection.createStatement
See Also: jdbcResultSet |
| Field Summary | |
| protected Result | batchResultOut
| | protected jdbcConnection | connection
The connection used to execute this statement. | | volatile boolean | isClosed
Whether this Statement has been explicitly closed. | | protected int | maxRows
The maximum number of rows to generate when executing this statement. | | protected Result | resultIn
The result of executing this statement. | | protected Result | resultOut
Used by this statement to communicate non-batched requests. | | protected int | rsType
The result set type obtained by executing this statement. |
| Constructor Summary | |
| | jdbcStatement(jdbcConnection c, int type)
Constructs a new jdbcStatement with the specified connection and
result type. |
| Method Summary | |
| public void | addBatch(String sql)
Adds the given SQL command to the current list of commmands for this
Statement object. | | public void | cancel()
Cancels this Statement object 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. | | void | checkClosed()
An internal check for closed statements. | | public void | clearBatch()
Empties this Statement object's current list of
SQL commands.
NOTE: This method is optional. | | public void | clearWarnings()
Clears all the warnings reported on this Statement
object. | | public synchronized void | close()
Releases this Statement object'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 method close on a Statement
object that is already closed has no effect.
Note: A Statement object is automatically closed
when it is garbage collected. | | public boolean | execute(String sql)
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. | | public boolean | execute(String sql, int autoGeneratedKeys)
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. | | public boolean | execute(String sql, int[] columnIndexes)
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. | | public boolean | execute(String sql, String[] columnNames)
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. | | public int[] | executeBatch()
Submits a batch of commands to the database for execution and
if all commands execute successfully, returns an array of update counts.
The int elements 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 method executeBatch
may be one of the following:
- 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 a BatchUpdateException, and a JDBC
driver may or may not continue to process the remaining commands in
the batch. | | public ResultSet | executeQuery(String sql)
Executes the given SQL statement, which returns a single
ResultSet object. | | public int | executeUpdate(String sql)
Executes the given SQL statement, which may be an INSERT,
UPDATE, or DELETE statement or an
SQL statement that returns nothing, such as an SQL DDL statement. | | public int | executeUpdate(String sql, int autoGeneratedKeys)
Executes the given SQL statement and signals the driver with the
given flag about whether the
auto-generated keys produced by this Statement object
should be made available for retrieval. | | public int | executeUpdate(String sql, int[] columnIndexes)
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. | | public int | executeUpdate(String sql, String[] columnNames)
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. | | public Connection | getConnection()
Retrieves the Connection object
that produced this Statement object. | | public int | getFetchDirection()
Retrieves the direction for fetching rows from
database tables that is the default for result sets
generated from this Statement object.
If this Statement object has not set
a fetch direction by calling the method setFetchDirection,
the return value is implementation-specific. | | public int | getFetchSize()
Retrieves the number of result set rows that is the default
fetch size for ResultSet objects
generated from this Statement object.
If this Statement object has not set
a fetch size by calling the method setFetchSize,
the return value is implementation-specific. | | public ResultSet | getGeneratedKeys()
Retrieves any auto-generated keys created as a result of executing this
Statement object. | | public int | getMaxFieldSize()
Retrieves the maximum number of bytes that can be
returned for character and binary column values in a ResultSet
object produced by this Statement object.
This limit applies only to BINARY,
VARBINARY, LONGVARBINARY, CHAR,
VARCHAR, and LONGVARCHAR
columns. | | public int | getMaxRows()
Retrieves the maximum number of rows that a
ResultSet object produced by this
Statement object can contain. | | public boolean | getMoreResults()
Moves to this Statement object's next result, returns
true if it is a ResultSet object, and
implicitly closes any current ResultSet
object(s) obtained with the method getResultSet. | | public boolean | getMoreResults(int current)
Moves to this Statement object's next result, deals with
any current ResultSet object(s) according to the instructions
specified by the given flag, and returns
true if the next result is a ResultSet object.
There are no more results when the following is true:
(!getMoreResults() && (getUpdateCount() == -1)
HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature. | | public int | getQueryTimeout()
Retrieves the number of seconds the driver will
wait for a Statement object to execute. | | public ResultSet | getResultSet()
Retrieves the current result as a ResultSet object.
This method should be called only once per result. | | public int | getResultSetConcurrency()
Retrieves the result set concurrency for ResultSet objects
generated by this Statement object. | | public int | getResultSetHoldability()
Retrieves the result set holdability for ResultSet objects
generated by this Statement object. | | public int | getResultSetType()
Retrieves the result set type for ResultSet objects
generated by this Statement object. | | public int | getUpdateCount()
Retrieves the current result as an update count;
if the result is a ResultSet object or there are no more results, -1
is returned. | | public SQLWarning | getWarnings()
Retrieves the first warning reported by calls on this Statement object.
Subsequent Statement object warnings will be chained to this
SQLWarning object.
The warning chain is automatically cleared each time
a statement is (re)executed. | | synchronized boolean | isClosed()
Retrieves whether this statement is closed. | | public void | setCursorName(String name)
Sets the SQL cursor name to the given String, which
will be used by subsequent Statement object
execute methods. | | public void | setEscapeProcessing(boolean enable)
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 for
PreparedStatements objects will have no effect. | | public void | setFetchDirection(int direction)
Gives the driver a hint as to the direction in which
rows will be processed in ResultSet
objects created using this Statement object. | | public void | setFetchSize(int rows)
Gives the JDBC driver a hint as to the number of rows that should
be fetched from the database when more rows are needed. | | public void | setMaxFieldSize(int max)
Sets the limit for the maximum number of bytes in a ResultSet
column storing character or binary values to
the given number of bytes. | | public void | setMaxRows(int max)
Sets the limit for the maximum number of rows that any
ResultSet object can contain to the given number.
If the limit is exceeded, the excess
rows are silently dropped. | | public void | setQueryTimeout(int seconds)
Sets the number of seconds the driver will wait for a
Statement object to execute to the given number of seconds.
If the limit is exceeded, an SQLException is thrown. |
| batchResultOut | | protected Result batchResultOut(Code) | | Use by this statement to communicate batched execution requests
|
| isClosed | | volatile boolean isClosed(Code) | | Whether this Statement has been explicitly closed. A jdbcConnection
object now explicitly closes all of its open jdbcXXXStatement objects
when it is closed.
|
| maxRows | | protected int maxRows(Code) | | The maximum number of rows to generate when executing this statement.
|
| resultIn | | protected Result resultIn(Code) | | The result of executing this statement.
|
| resultOut | | protected Result resultOut(Code) | | Used by this statement to communicate non-batched requests.
|
| rsType | | protected int rsType(Code) | | The result set type obtained by executing this statement.
|
| jdbcStatement | | jdbcStatement(jdbcConnection c, int type)(Code) | | Constructs a new jdbcStatement with the specified connection and
result type.
Parameters:
c - the connection on which this statement will execute
Parameters:
type - the kind of results this will return |
| addBatch | | public void addBatch(String sql) throws SQLException(Code) | |
Adds the given SQL command to the current list of commmands for this
Statement object. The commands in this list can be
executed as a batch by calling the method executeBatch.
NOTE: This method is optional.
HSQLDB-Specific Information:
Starting with 1.7.2, this feature is supported.
Parameters:
sql - typically this is a static SQL INSERT orUPDATE statement
exception:
SQLException - if a database access error occurs, or thedriver does not support batch updates
See Also: jdbcStatement.executeBatch
since:
JDK 1.2 (JDK 1.1.x developers: read the new overview
since:
for jdbcStatement) |
| cancel | | public void cancel() throws SQLException(Code) | |
Cancels this Statement object 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.
HSQLDB-Specific Information:
Including 1.7.2, HSQLDB does not support aborting a SQL
statement; calls to this method are ignored.
exception:
SQLException - if a database access error occurs |
| checkClosed | | void checkClosed() throws SQLException(Code) | | An internal check for closed statements.
throws:
SQLException - when the connection is closed |
| clearBatch | | public void clearBatch() throws SQLException(Code) | |
Empties this Statement object's current list of
SQL commands.
NOTE: This method is optional.
HSQLDB-Specific Information:
Starting with HSQLDB 1.7.2, this feature is supported.
exception:
SQLException - if a database access error occurs or thedriver does not support batch updates
See Also: jdbcStatement.addBatch
since:
JDK 1.2 (JDK 1.1.x developers: read the new overview
since:
for jdbcStatement) |
| clearWarnings | | public void clearWarnings() throws SQLException(Code) | |
Clears all the warnings reported on this Statement
object. After a call to this method,
the method getWarnings will return
null until a new warning is reported for this
Statement object.
HSQLDB-Specific Information:
Including HSQLDB 1.7.2, SQLWarning objects are
never produced for Statement Objects; calls to this method are
ignored.
exception:
SQLException - if a database access error occurs |
| close | | public synchronized void close() throws SQLException(Code) | |
Releases this Statement object'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 method close on a Statement
object that is already closed has no effect.
Note: A Statement object is automatically closed
when it is garbage collected. When a Statement object is
closed, its current ResultSet object, if one exists, is
also closed.
exception:
SQLException - if a database access error occurs |
| execute | | public boolean execute(String sql) throws SQLException(Code) | |
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.
The execute method executes an SQL statement and indicates the
form of the first result. You must then use the methods
getResultSet or getUpdateCount
to retrieve the result, and getMoreResults to
move to any subsequent result(s).
Parameters:
sql - any SQL statement true if the first result is a ResultSetobject; false if it is an update count or there areno results
exception:
SQLException - if a database access error occurs
See Also: jdbcStatement.getResultSet
See Also: jdbcStatement.getUpdateCount
See Also: jdbcStatement.getMoreResults |
| execute | | public boolean execute(String sql, int autoGeneratedKeys) throws SQLException(Code) | |
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 an INSERT statement.
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.
The execute method executes an SQL statement and indicates the
form of the first result. You must then use the methods
getResultSet or getUpdateCount
to retrieve the result, and getMoreResults to
move to any subsequent result(s).
HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature.
Calling this method always throws an SQLException,
stating that the function is not supported.
Parameters:
sql - any SQL statement
Parameters:
autoGeneratedKeys - a constant indicating whether auto-generatedkeys should be made available for retrieval using the methodgetGeneratedKeys; one of the following constants:Statement.RETURN_GENERATED_KEYS orStatement.NO_GENERATED_KEYS true if the first result is a ResultSetobject; false if it is an update count or there areno results
exception:
SQLException - if a database access error occurs
See Also: jdbcStatement.getResultSet
See Also: jdbcStatement.getUpdateCount
See Also: jdbcStatement.getMoreResults
See Also: jdbcStatement.getGeneratedKeys
since:
JDK 1.4, HSQLDB 1.7 |
| execute | | public boolean execute(String sql, int[] columnIndexes) throws SQLException(Code) | |
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 an INSERT statement.
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.
The execute method executes an SQL statement and indicates the
form of the first result. You must then use the methods
getResultSet or getUpdateCount
to retrieve the result, and getMoreResults to
move to any subsequent result(s).
HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature.
Calling this method always throws an SQLException,
stating that the function is not supported.
Parameters:
sql - any SQL statement
Parameters:
columnIndexes - an array of the indexes of the columns in theinserted row that should be made available for retrieval by acall to the method getGeneratedKeys true if the first result is a ResultSetobject; false if it is an update count or thereare no results
exception:
SQLException - if a database access error occurs
See Also: jdbcStatement.getResultSet
See Also: jdbcStatement.getUpdateCount
See Also: jdbcStatement.getMoreResults
since:
JDK 1.4, HSQLDB 1.7 |
| execute | | public boolean execute(String sql, String[] columnNames) throws SQLException(Code) | |
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 an INSERT statement.
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.
The execute method executes an SQL statement and indicates the
form of the first result. You must then use the methods
getResultSet or getUpdateCount
to retrieve the result, and getMoreResults to
move to any subsequent result(s).
HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature.
Calling this method always throws an SQLException,
stating that the function is not supported.
Parameters:
sql - any SQL statement
Parameters:
columnNames - an array of the names of the columns in the insertedrow that should be made available for retrieval by a call to themethod getGeneratedKeys true if the next result is a ResultSetobject; false if it is an update count or thereare no more results
exception:
SQLException - if a database access error occurs
See Also: jdbcStatement.getResultSet
See Also: jdbcStatement.getUpdateCount
See Also: jdbcStatement.getMoreResults
See Also: jdbcStatement.getGeneratedKeys
since:
JDK 1.4, HSQLDB 1.7 |
| executeBatch | | public int[] executeBatch() throws SQLException(Code) | |
Submits a batch of commands to the database for execution and
if all commands execute successfully, returns an array of update counts.
The int elements 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 method executeBatch
may be one of the following:
- 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 a BatchUpdateException, 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 method
BatchUpdateException.getUpdateCounts
will 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 fails
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 BatchUpdateException obejct has been thrown.
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.
an array of update counts containing one element for eachcommand in the batch. The elements of the array are ordered accordingto the order in which commands were added to the batch.
exception:
SQLException - if a database access error occurs or thedriver does not support batch statements. Throwsjava.sql.BatchUpdateException(a subclass of java.sql.SQLException) if one of the commandssent to the database fails to execute properly or attempts to return aresult set.
since:
JDK 1.3 (JDK 1.1.x developers: read the new overview
since:
for jdbcStatement) |
| executeQuery | | public ResultSet executeQuery(String sql) throws SQLException(Code) | |
Executes the given SQL statement, which returns a single
ResultSet object.
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 astatic SQL SELECT statement a ResultSet object that contains the data producedby the given query; never null
exception:
SQLException - if a database access error occurs or the givenSQL statement produces anything other than a singleResultSet object |
| executeUpdate | | public int executeUpdate(String sql) throws SQLException(Code) | |
Executes the given SQL statement, which may be an INSERT,
UPDATE, or DELETE statement or an
SQL statement that returns nothing, such as an SQL DDL statement.
Parameters:
sql - an SQL INSERT, UPDATE orDELETE statement or an SQL statement that returns nothing either the row count for INSERT, UPDATEor DELETE statements, or 0 for SQL statementsthat return nothing
exception:
SQLException - if a database access error occurs or the givenSQL statement produces a ResultSet object |
| executeUpdate | | public int executeUpdate(String sql, int autoGeneratedKeys) throws SQLException(Code) | |
Executes the given SQL statement and signals the driver with the
given flag about whether the
auto-generated keys produced by this Statement object
should be made available for retrieval.
HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature.
Calling this method always throws an SQLException,
stating that the function is not supported.
Parameters:
sql - must be an SQL INSERT, UPDATE orDELETE statement or an SQL statement thatreturns nothing
Parameters:
autoGeneratedKeys - a flag indicating whether auto-generated keysshould be made available for retrieval;one of the following constants:Statement.RETURN_GENERATED_KEYSStatement.NO_GENERATED_KEYS either the row count for INSERT, UPDATEor DELETE statements, or 0 for SQLstatements that return nothing
exception:
SQLException - if a database access error occurs, the givenSQL statement returns a ResultSet object, orthe given constant is not one of those allowed
since:
JDK 1.4, HSQLDB 1.7 |
| executeUpdate | | public int executeUpdate(String sql, int[] columnIndexes) throws SQLException(Code) | |
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 an INSERT statement.
HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature.
Calling this method always throws an SQLException,
stating that the function is not supported.
Parameters:
sql - an SQL INSERT, UPDATE orDELETE statement or an SQL statement that returns nothing,such as an SQL DDL statement
Parameters:
columnIndexes - an array of column indexes indicating the columnsthat should be returned from the inserted row either the row count for INSERT, UPDATE,or DELETE statements, or 0 for SQL statementsthat return nothing
exception:
SQLException - if a database access error occurs or the SQLstatement returns a ResultSet object
since:
JDK 1.4, HSQLDB 1.7 |
| executeUpdate | | public int executeUpdate(String sql, String[] columnNames) throws SQLException(Code) | |
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 an INSERT statement.
HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature.
Calling this method always throws an SQLException,
stating that the function is not supported.
Parameters:
sql - an SQL INSERT, UPDATE orDELETE statement or an SQL statement that returns nothing
Parameters:
columnNames - an array of the names of the columns that should bereturned from the inserted row either the row count for INSERT, UPDATE,or DELETE statements, or 0 for SQL statementsthat return nothing
exception:
SQLException - if a database access error occurs
since:
JDK 1.4, HSQLDB 1.7 |
| getConnection | | public Connection getConnection() throws SQLException(Code) | |
Retrieves the Connection object
that produced this Statement object.
the connection that produced this statement
exception:
SQLException - if a database access error occurs
since:
JDK 1.2 (JDK 1.1.x developers: read the new overview
since:
for jdbcStatement) |
| getFetchDirection | | public int getFetchDirection() throws SQLException(Code) | |
Retrieves the direction for fetching rows from
database tables that is the default for result sets
generated from this Statement object.
If this Statement object has not set
a fetch direction by calling the method setFetchDirection,
the return value is implementation-specific.
HSQLDB-Specific Information:
Including 1.7.2, HSQLDB always returns FETCH_FORWARD.
the default fetch direction for result sets generatedfrom this Statement object
exception:
SQLException - if a database access error occurs
since:
JDK 1.2 (JDK 1.1.x developers: read the new overview
since:
for jdbcStatement)
See Also: jdbcStatement.setFetchDirection |
| getFetchSize | | public int getFetchSize() throws SQLException(Code) | |
Retrieves the number of result set rows that is the default
fetch size for ResultSet objects
generated from this Statement object.
If this Statement object has not set
a fetch size by calling the method setFetchSize,
the return value is implementation-specific.
HSQLDB-Specific Information
Including 1.7.2, this method always returns 0.
HSQLDB fetches each result completely as part of
executing its statement
the default fetch size for result sets generatedfrom this Statement object
exception:
SQLException - if a database access error occurs
since:
JDK 1.2 (JDK 1.1.x developers: read the new overview
since:
for jdbcStatement)
See Also: jdbcStatement.setFetchSize |
| getGeneratedKeys | | public ResultSet getGeneratedKeys() throws SQLException(Code) | |
Retrieves any auto-generated keys created as a result of executing this
Statement object. If this Statement object did
not generate any keys, an empty ResultSet
object is returned.
HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature.
Calling this method always throws an SQLException,
stating that the function is not supported.
a ResultSet object containing the auto-generated key(s)generated by the execution of this Statement object
exception:
SQLException - if a database access error occurs
since:
JDK 1.4, HSQLDB 1.7 |
| getMaxFieldSize | | public int getMaxFieldSize() throws SQLException(Code) | |
Retrieves the maximum number of bytes that can be
returned for character and binary column values in a ResultSet
object produced by this Statement object.
This limit applies only to BINARY,
VARBINARY, LONGVARBINARY, CHAR,
VARCHAR, and LONGVARCHAR
columns. If the limit is exceeded, the excess data is silently
discarded.
HSQLDB-Specific Information:
Including 1.7.2, HSQLDB always returns zero, meaning there
is no limit.
the current column size limit for columns storing character andbinary values; zero means there is no limit
exception:
SQLException - if a database access error occurs
See Also: jdbcStatement.setMaxFieldSize |
| getMaxRows | | public int getMaxRows() throws SQLException(Code) | |
Retrieves the maximum number of rows that a
ResultSet object produced by this
Statement object can contain. If this limit is exceeded,
the excess rows are silently dropped.
the current maximum number of rows for a ResultSetobject produced by this Statement object;zero means there is no limit
exception:
SQLException - if a database access error occurs
See Also: jdbcStatement.setMaxRows |
| getMoreResults | | public boolean getMoreResults() throws SQLException(Code) | |
Moves to this Statement object's next result, returns
true if it is a ResultSet object, and
implicitly closes any current ResultSet
object(s) obtained with the method getResultSet.
There are no more results when the following is true:
(!getMoreResults() && (getUpdateCount() == -1)
true if the next result is a ResultSetobject; false if it is an update count or there areno more results
exception:
SQLException - if a database access error occurs
See Also: jdbcStatement.execute |
| getMoreResults | | public boolean getMoreResults(int current) throws SQLException(Code) | |
Moves to this Statement object's next result, deals with
any current ResultSet object(s) according to the instructions
specified by the given flag, and returns
true if the next result is a ResultSet object.
There are no more results when the following is true:
(!getMoreResults() && (getUpdateCount() == -1)
HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support this feature.
Calling this method always throws an SQLException,
stating that the function is not supported.
Parameters:
current - one of the following Statementconstants indicating what should happen to currentResultSet objects obtained using the methodgetResultSetCLOSE_CURRENT_RESULT,KEEP_CURRENT_RESULT, orCLOSE_ALL_RESULTS true if the next result is a ResultSetobject; false if it is an update count or there are nomore results
exception:
SQLException - if a database access error occurs
since:
JDK 1.4, HSQLDB 1.7
See Also: jdbcStatement.execute |
| getQueryTimeout | | public int getQueryTimeout() throws SQLException(Code) | |
Retrieves the number of seconds the driver will
wait for a Statement object to execute. If the
limit is exceeded, an SQLException is thrown.
HSQLDB-Specific Information:
Including 1.7.2, HSQLDB always returns zero, meaning there
is no limit.
the current query timeout limit in seconds; zero means there isno limit
exception:
SQLException - if a database access error occurs
See Also: jdbcStatement.setQueryTimeout |
| getResultSet | | public ResultSet getResultSet() throws SQLException(Code) | |
Retrieves the current result as a ResultSet object.
This method should be called only once per result.
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.
the current result as a ResultSet object ornull if the result is an update count or thereare no more results
exception:
SQLException - if a database access error occurs
See Also: jdbcStatement.execute |
| getResultSetConcurrency | | public int getResultSetConcurrency() throws SQLException(Code) | |
Retrieves the result set concurrency for ResultSet objects
generated by this Statement object.
HSQLDB-Specific Information:
Including 1.7.2, HSQLDB supports only
CONCUR_READ_ONLY concurrency.
either ResultSet.CONCUR_READ_ONLY orResultSet.CONCUR_UPDATABLE (not supported)
exception:
SQLException - if a database access error occurs
since:
JDK 1.2 (JDK 1.1.x developers: read the new overview
since:
for jdbcStatement) |
| getResultSetHoldability | | public int getResultSetHoldability() throws SQLException(Code) | |
Retrieves the result set holdability for ResultSet objects
generated by this Statement object.
HSQLDB-Specific Information:
Starting with 1.7.2, this method returns HOLD_CURSORS_OVER_COMMIT
either ResultSet.HOLD_CURSORS_OVER_COMMIT orResultSet.CLOSE_CURSORS_AT_COMMIT
exception:
SQLException - if a database access error occurs
since:
JDK 1.4, HSQLDB 1.7 |
| getResultSetType | | public int getResultSetType() throws SQLException(Code) | |
Retrieves the result set type for ResultSet objects
generated by this Statement object.
HSQLDB-Specific Information:
HSQLDB 1.7.0 and later versions support TYPE_FORWARD_ONLY
and TYPE_SCROLL_INSENSITIVE.
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
exception:
SQLException - if a database access error occurs
since:
JDK 1.2 (JDK 1.1.x developers: read the new overview
since:
for jdbcStatement) |
| getUpdateCount | | public int getUpdateCount() throws SQLException(Code) | |
Retrieves the current result as an update count;
if the result is a ResultSet object or there are no more results, -1
is returned. This method should be called only once per result.
the current result as an update count; -1 if the current result is aResultSet object or there are no more results
exception:
SQLException - if a database access error occurs
See Also: jdbcStatement.execute |
| getWarnings | | public SQLWarning getWarnings() throws SQLException(Code) | |
Retrieves the first warning reported by calls on this Statement object.
Subsequent Statement object warnings will be chained to this
SQLWarning object.
The warning chain is automatically cleared each time
a statement is (re)executed. This method may not be called on a closed
Statement object; doing so will cause an SQLException
to be thrown.
Note: If you are processing a ResultSet object, any
warnings associated with reads on that ResultSet object
will be chained on it rather than on the Statement
object that produced it.
HSQLDB-Specific Information:
Including 1.7.2, HSQLDB never produces Statement warnings;
this method always returns null.
the first SQLWarning object or nullif there are no warnings
exception:
SQLException - if a database access error occurs or thismethod is called on a closed statement |
| isClosed | | synchronized boolean isClosed()(Code) | | Retrieves whether this statement is closed.
|
| setCursorName | | public void setCursorName(String name) throws SQLException(Code) | |
Sets the SQL cursor name to the given String, which
will be used by subsequent Statement object
execute methods. This name can then be
used in SQL positioned update or delete statements to identify the
current row in the ResultSet object 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's SELECT statement
should have the form SELECT FOR UPDATE. If
FOR UPDATE is not present, positioned updates may fail.
Note: By definition, the execution of positioned updates and
deletes must be done by a different Statement object than
the one that generated the ResultSet object being used for
positioning. Also, cursor names must be unique within a connection.
HSQLDB-Specific Information:
Including 1.7.2, HSQLDB does not support named cursors,
updateable results or table locking via SELECT FOR UPDATE;
calls to this method are ignored.
Parameters:
name - the new cursor name, which must be unique withina connection
exception:
SQLException - if a database access error occurs |
| setEscapeProcessing | | public void setEscapeProcessing(boolean enable) throws SQLException(Code) | |
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 for
PreparedStatements objects will have no effect.
Parameters:
enable - true to enable escape processing;false to disable it
exception:
SQLException - if a database access error occurs |
| setFetchDirection | | public void setFetchDirection(int direction) throws SQLException(Code) | |
Gives the driver a hint as to the direction in which
rows will be processed in ResultSet
objects created using this Statement object. The
default value is ResultSet.FETCH_FORWARD.
Note that this method sets the default fetch direction for
result sets generated by this Statement object.
Each result set has its own methods for getting and setting
its own fetch direction.
HSQLDB-Specific Information:
Including 1.7.2, HSQLDB supports only FETCH_FORWARD.
Setting any other value will throw an SQLException
stating that the operation is not supported.
Parameters:
direction - the initial direction for processing rows
exception:
SQLException - if a database access error occursor the given directionis not one of ResultSet.FETCH_FORWARD,ResultSet.FETCH_REVERSE, orResultSet.FETCH_UNKNOWN HSQLDB throws for all values except FETCH_FORWARD
since:
JDK 1.2 (JDK 1.1.x developers: read the new overview
since:
for jdbcStatement)
See Also: jdbcStatement.getFetchDirection |
| setFetchSize | | public void setFetchSize(int rows) throws SQLException(Code) | |
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.
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
exception:
SQLException - if a database access error occurs, or thecondition 0 <= rows <= this.getMaxRows()is not satisfied. HSQLDB never throws an exception, since calls to this methodare always ignored.
since:
JDK 1.2 (JDK 1.1.x developers: read the new overview
since:
for jdbcStatement)
See Also: jdbcStatement.getFetchSize |
| setMaxFieldSize | | public void setMaxFieldSize(int max) throws SQLException(Code) | |
Sets the limit for the maximum number of bytes in a ResultSet
column storing character or binary values to
the given number of bytes. This limit applies
only to BINARY, VARBINARY,
LONGVARBINARY, CHAR, VARCHAR, and
LONGVARCHAR fields. If the limit is exceeded, the excess data
is silently discarded. For maximum portability, use values
greater than 256.
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
exception:
SQLException - if a database access error occursor the condition max >= 0 is not satisfied
See Also: jdbcStatement.getMaxFieldSize |
| setMaxRows | | public void setMaxRows(int max) throws SQLException(Code) | |
Sets the limit for the maximum number of rows that any
ResultSet object can contain to the given number.
If the limit is exceeded, the excess
rows are silently dropped.
Parameters:
max - the new max rows limit; zero means there is no limit
exception:
SQLException - if a database access error occursor the condition max >= 0 is not satisfied
See Also: jdbcStatement.getMaxRows |
| setQueryTimeout | | public void setQueryTimeout(int seconds) throws SQLException(Code) | |
Sets the number of seconds the driver will wait for a
Statement object to execute to the given number of seconds.
If the limit is exceeded, an SQLException is thrown.
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 meansthere is no limit
exception:
SQLException - if a database access error occursor the condition seconds >= 0 is not satisfied
See Also: jdbcStatement.getQueryTimeout |
|
|