Methods Summary |
---|
public void | addBatch(java.lang.String sql)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.
jdbcStatement.addBatch(sql);
|
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.
jdbcStatement.cancel();
|
public void | clearBatch()Empties this Statement object's current list of
SQL commands.
NOTE: This method is optional.
jdbcStatement.clearBatch();
|
public void | clearWarnings()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.
jdbcStatement.clearWarnings();
|
public 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. When a Statement object is
closed, its current ResultSet object, if one exists, is
also closed.
jdbcStatement.close();
|
public boolean | execute(java.lang.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. 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).
return jdbcStatement.execute(sql);
|
public boolean | execute(java.lang.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. 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).
return jdbcStatement.execute(sql, autoGeneratedKeys);
|
public boolean | execute(java.lang.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. 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).
return jdbcStatement.execute(sql, columnIndexes);
|
public boolean | execute(java.lang.String sql, java.lang.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. 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).
return jdbcStatement.execute(sql, columnNames);
|
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. 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.
return jdbcStatement.executeBatch();
|
public int | executeUpdate(java.lang.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.
return jdbcStatement.executeUpdate(sql);
|
public int | executeUpdate(java.lang.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.
return jdbcStatement.executeUpdate(sql, autoGeneratedKeys);
|
public int | executeUpdate(java.lang.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. The driver will ignore the array if the SQL statement
is not an INSERT statement.
return jdbcStatement.executeUpdate(sql, columnIndexes);
|
public int | executeUpdate(java.lang.String sql, java.lang.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. The driver will ignore the array if the SQL statement
is not an INSERT statement.
return jdbcStatement.executeUpdate(sql, columnNames);
|
public java.sql.Connection | getActualConnection()Returns the underlying physical connection.
return jdbcStatement.getConnection();
|
public java.sql.Connection | getConnection()Retrieves the Connection object
that produced this Statement object.
return connection;
|
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.
return jdbcStatement.getFetchDirection();
|
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.
return jdbcStatement.getFetchSize();
|
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. If the limit is exceeded, the excess data is silently
discarded.
return jdbcStatement.getMaxFieldSize();
|
public int | getMaxRows()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.
return jdbcStatement.getMaxRows();
|
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 .
There are no more results when the following is true:
// stmt is a Statement object
((stmt.getMoreResults() == false) && (stmt.getUpdateCount() == -1))
return jdbcStatement.getMoreResults();
|
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:
// stmt is a Statement object
((stmt.getMoreResults() == false) && (stmt.getUpdateCount() == -1))
return jdbcStatement.getMoreResults(current);
|
public int | getQueryTimeout()Retrieves the number of seconds the driver will
wait for a Statement object to execute. If the limit is exceeded, a
SQLException is thrown.
return jdbcStatement.getQueryTimeout();
|
public int | getResultSetConcurrency()Retrieves the result set concurrency for ResultSet objects
generated by this Statement object.
return jdbcStatement.getResultSetConcurrency();
|
public int | getResultSetHoldability()Retrieves the result set holdability for ResultSet objects
generated by this Statement object.
return jdbcStatement.getResultSetHoldability();
|
public int | getResultSetType()Retrieves the result set type for ResultSet objects
generated by this Statement object.
return jdbcStatement.getResultSetType();
|
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. This method should be called only once per result.
return jdbcStatement.getUpdateCount();
|
public java.sql.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. 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.
return jdbcStatement.getWarnings();
|
public void | setCursorName(java.lang.String name)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.
jdbcStatement.setCursorName(name);
|
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.
jdbcStatement.setEscapeProcessing(enable);
|
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. 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.
jdbcStatement.setFetchDirection(direction);
|
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. 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.
jdbcStatement.setFetchDirection(rows);
|
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. 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.
jdbcStatement.setMaxFieldSize(max);
|
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.
jdbcStatement.setMaxFieldSize(max);
|
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.
jdbcStatement.setQueryTimeout(seconds);
|