Class jdbcPreparedStatement
- java.lang.Object
-
- org.hsqldb.jdbc.jdbcStatement
-
- org.hsqldb.jdbc.jdbcPreparedStatement
-
- All Implemented Interfaces:
java.lang.AutoCloseable
,java.sql.PreparedStatement
,java.sql.Statement
,java.sql.Wrapper
- Direct Known Subclasses:
jdbcCallableStatement
public class jdbcPreparedStatement extends jdbcStatement implements java.sql.PreparedStatement
An object that represents a precompiled SQL statement.An SQL statement is precompiled and stored in a
PreparedStatement
object. This object can then be used to efficiently execute this statement multiple times.Note: The setter methods (
setShort
,setString
, and so on) for setting IN parameter values must specify types that are compatible with the defined SQL type of the input parameter. For instance, if the IN parameter has SQL typeINTEGER
, then the methodsetInt
should be used.If arbitrary parameter type conversions are required, the method
setObject
should be used with a target SQL type.In the following example of setting a parameter,
con
represents an active connection:PreparedStatement pstmt = con.prepareStatement("UPDATE EMPLOYEES SET SALARY = ? WHERE ID = ?"); pstmt.setBigDecimal(1, 153833.00) pstmt.setInt(2, 110592)
HSQLDB-Specific Information:
Starting with HSQLDB 1.7.2, jdbcPreparedStatement objects are backed by a true compiled parameteric representation. Hence, there are now significant performance gains to be had by using a jdbcPreparedStatement object in preference to a jdbcStatement object, if a short-running SQL statement is to be executed more than a small number of times.
When it can be otherwise avoided, it is to be considered poor practice to fully prepare (construct), parameterize, execute, fetch and close a jdbcPreparedStatement object for each execution cycle. Indeed, under HSQLDB 1.8.0, this practice is likely to be noticably less performant for short-running statements than the equivalent process using jdbcStatement objects, albeit far more convenient, less error prone and certainly much less resource-intensive, especially when large binary and character values are involved, due to the optimized parameterization facility.
Instead, when developing an application that is not totally oriented toward the execution of ad hoc SQL, it is recommended to expend some effort toward identifing the SQL statements that are good candidates for regular reuse and adapting the structure of the application accordingly. Often, this is done by recording the text of candidate SQL statements in an application resource object (which has the nice side-benefit of isolating and hiding differences in SQL dialects across different drivers) and caching for possible reuse the PreparedStatement objects derived from the recorded text.
Multi thread use:
A PreparedStatement object is stateful and should not normally be shared by multiple threads. If it has to be shared, the calls to set the parameters, calls to add batch statements, the execute call and any post-execute calls should be made within a block synchronized on the PreparedStatement Object.
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, it is possible to build the product so that all JDBC 2 methods can be called while executing under the version 1.1.x Java Runtime EnvironmentTM. However, in addition to requiring explicit casts to the org.hsqldb.jdbcXXX interface implementations, some of these method calls require
int
values that are defined only in the JDBC 2 or greater version ofResultSet
interface. For this reason, when the product is compiled under JDK 1.1.x, these values are defined injdbcResultSet
.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 in such a manner will not be compatible for use with other JDBC 2 drivers, since they expect and useResultSet
, rather thanjdbcResultSet
. Also note, 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, fredt@users
- See Also:
jdbcConnection.prepareStatement(java.lang.String)
,jdbcResultSet
-
-
Method Summary
All Methods Instance Methods Concrete Methods Deprecated Methods Modifier and Type Method Description void
addBatch()
Adds a set of parameters to thisPreparedStatement
object's batch of commands.void
addBatch(java.lang.String sql)
This method should always throw if called for a PreparedStatement or CallableStatment.void
clearParameters()
Clears the current parameter values immediately.void
close()
Does the specialized work required to free this object's resources and that of it's parent class.boolean
execute()
Executes the SQL statement in thisPreparedStatement
object, which may be any kind of SQL statement.boolean
execute(java.lang.String sql)
This method should always throw if called for a PreparedStatement or CallableStatment.int[]
executeBatch()
Submits a batch of commands to the database for execution and if all commands execute successfully, returns an array of update counts.java.sql.ResultSet
executeQuery()
Executes the SQL query in thisPreparedStatement
object and returns theResultSet
object generated by the query.java.sql.ResultSet
executeQuery(java.lang.String sql)
This method should always throw if called for a PreparedStatement or CallableStatment.int
executeUpdate()
Executes the SQL statement in thisPreparedStatement
object, which must be an SQLINSERT
,UPDATE
orDELETE
statement; or an SQL statement that returns nothing, such as a DDL statement.int
executeUpdate(java.lang.String sql)
This method should always throw if called for a PreparedStatement or CallableStatment.java.sql.ResultSetMetaData
getMetaData()
Retrieves aResultSetMetaData
object that contains information about the columns of theResultSet
object that will be returned when thisPreparedStatement
object is executed.java.sql.ParameterMetaData
getParameterMetaData()
Retrieves the number, types and properties of thisPreparedStatement
object's parameters.boolean
isPoolable()
boolean
isWrapperFor(java.lang.Class<?> iface)
void
setArray(int i, java.sql.Array x)
Sets the designated parameter to the givenArray
object.void
setAsciiStream(int parameterIndex, java.io.InputStream x)
void
setAsciiStream(int parameterIndex, java.io.InputStream x, int length)
Sets the designated parameter to the given input stream, which will have the specified number of bytes.void
setAsciiStream(int parameterIndex, java.io.InputStream x, long length)
void
setBigDecimal(int parameterIndex, java.math.BigDecimal x)
Sets the designated parameter to the givenjava.math.BigDecimal
value.void
setBinaryStream(int parameterIndex, java.io.InputStream x)
void
setBinaryStream(int parameterIndex, java.io.InputStream x, int length)
Sets the designated parameter to the given input stream, which will have the specified number of bytes.void
setBinaryStream(int parameterIndex, java.io.InputStream x, long length)
void
setBlob(int parameterIndex, java.io.InputStream inputStream)
void
setBlob(int parameterIndex, java.io.InputStream inputStream, long length)
void
setBlob(int i, java.sql.Blob x)
Sets the designated parameter to the givenBlob
object.void
setBoolean(int parameterIndex, boolean x)
Sets the designated parameter to the given Javaboolean
value.void
setByte(int parameterIndex, byte x)
Sets the designated parameter to the given Javabyte
value.void
setBytes(int paramIndex, byte[] x)
Sets the designated parameter to the given Java array of bytes.void
setCharacterStream(int parameterIndex, java.io.Reader reader)
void
setCharacterStream(int parameterIndex, java.io.Reader reader, int length)
Sets the designated parameter to the givenReader
object, which is the given number of characters long.void
setCharacterStream(int parameterIndex, java.io.Reader reader, long length)
void
setClob(int parameterIndex, java.io.Reader reader)
void
setClob(int parameterIndex, java.io.Reader reader, long length)
void
setClob(int i, java.sql.Clob x)
Sets the designated parameter to the givenClob
object.void
setDate(int parameterIndex, java.sql.Date x)
Sets the designated parameter to the givenjava.sql.Date
value.void
setDate(int parameterIndex, java.sql.Date x, java.util.Calendar cal)
Sets the designated parameter to the givenjava.sql.Date
value, using the givenCalendar
object.void
setDouble(int parameterIndex, double x)
Sets the designated parameter to the given Javadouble
value.void
setEscapeProcessing(boolean enable)
Sets escape processing on or off.void
setFloat(int parameterIndex, float x)
Sets the designated parameter to the given Javafloat
value.void
setInt(int parameterIndex, int x)
Sets the designated parameter to the given Javaint
value.void
setLong(int parameterIndex, long x)
Sets the designated parameter to the given Javalong
value.void
setNCharacterStream(int parameterIndex, java.io.Reader value)
void
setNCharacterStream(int parameterIndex, java.io.Reader value, long length)
void
setNClob(int parameterIndex, java.io.Reader reader)
void
setNClob(int parameterIndex, java.io.Reader reader, long length)
void
setNClob(int parameterIndex, java.sql.NClob value)
void
setNString(int parameterIndex, java.lang.String value)
void
setNull(int paramIndex, int sqlType)
Sets the designated parameter to SQLNULL
.void
setNull(int paramIndex, int sqlType, java.lang.String typeName)
Sets the designated parameter to SQLNULL
.void
setObject(int parameterIndex, java.lang.Object x)
Sets the value of the designated parameter using the given object.void
setObject(int parameterIndex, java.lang.Object x, int targetSqlType)
Sets the value of the designated parameter with the given object.void
setObject(int parameterIndex, java.lang.Object x, int targetSqlType, int scale)
Sets the value of the designated parameter with the given object.void
setPoolable(boolean poolable)
void
setRef(int i, java.sql.Ref x)
Sets the designated parameter to the givenREF(<structured-type>)
value.void
setRowId(int parameterIndex, java.sql.RowId x)
void
setShort(int parameterIndex, short x)
Sets the designated parameter to the given Javashort
value.void
setSQLXML(int parameterIndex, java.sql.SQLXML xmlObject)
void
setString(int parameterIndex, java.lang.String x)
Sets the designated parameter to the given JavaString
value.void
setTime(int parameterIndex, java.sql.Time x)
Sets the designated parameter to the givenjava.sql.Time
value.void
setTime(int parameterIndex, java.sql.Time x, java.util.Calendar cal)
Sets the designated parameter to the givenjava.sql.Time
value, using the givenCalendar
object.void
setTimestamp(int parameterIndex, java.sql.Timestamp x)
Sets the designated parameter to the givenjava.sql.Timestamp
value.void
setTimestamp(int parameterIndex, java.sql.Timestamp x, java.util.Calendar cal)
Sets the designated parameter to the givenjava.sql.Timestamp
value, using the givenCalendar
object.void
setUnicodeStream(int parameterIndex, java.io.InputStream x, int length)
Deprecated.Sun does not include a reason, but presumably this is because setCharacterStream is now preferedvoid
setURL(int parameterIndex, java.net.URL x)
Sets the designated parameter to the givenjava.net.URL
value.java.lang.String
toString()
Retrieves a String representation of this object.<T> T
unwrap(java.lang.Class<T> iface)
-
Methods inherited from class org.hsqldb.jdbc.jdbcStatement
cancel, clearBatch, clearWarnings, closeOnCompletion, execute, execute, execute, executeUpdate, executeUpdate, executeUpdate, getConnection, getFetchDirection, getFetchSize, getGeneratedKeys, getMaxFieldSize, getMaxRows, getMoreResults, getMoreResults, getQueryTimeout, getResultSet, getResultSetConcurrency, getResultSetHoldability, getResultSetType, getUpdateCount, getWarnings, isClosed, isCloseOnCompletion, setCursorName, setFetchDirection, setFetchSize, setMaxFieldSize, setMaxRows, setQueryTimeout
-
Methods inherited from class java.lang.Object
equals, getClass, hashCode, notify, notifyAll, wait, wait, wait
-
Methods inherited from interface java.sql.PreparedStatement
executeLargeUpdate, setObject, setObject
-
Methods inherited from interface java.sql.Statement
cancel, clearBatch, clearWarnings, closeOnCompletion, enquoteIdentifier, enquoteLiteral, enquoteNCharLiteral, execute, execute, execute, executeLargeBatch, executeLargeUpdate, executeLargeUpdate, executeLargeUpdate, executeLargeUpdate, executeUpdate, executeUpdate, executeUpdate, getConnection, getFetchDirection, getFetchSize, getGeneratedKeys, getLargeMaxRows, getLargeUpdateCount, getMaxFieldSize, getMaxRows, getMoreResults, getMoreResults, getQueryTimeout, getResultSet, getResultSetConcurrency, getResultSetHoldability, getResultSetType, getUpdateCount, getWarnings, isClosed, isCloseOnCompletion, isSimpleIdentifier, setCursorName, setFetchDirection, setFetchSize, setLargeMaxRows, setMaxFieldSize, setMaxRows, setQueryTimeout
-
-
-
-
Method Detail
-
setEscapeProcessing
public void setEscapeProcessing(boolean enable) throws java.sql.SQLException
Sets escape processing on or off.HSQLDB-Specific Information:
Since 1.7.0, the implementation follows the standard behaviour by overriding the same method in jdbcStatement class.
In other words, calling this method has no effect.
- Specified by:
setEscapeProcessing
in interfacejava.sql.Statement
- Overrides:
setEscapeProcessing
in classjdbcStatement
- Parameters:
enable
-true
to enable escape processing;false
to disable it- Throws:
java.sql.SQLException
- if a database access error occurs
-
execute
public boolean execute() throws java.sql.SQLException
Executes the SQL statement in thisPreparedStatement
object, which may be any kind of SQL statement. Some prepared statements return multiple results; theexecute
method handles these complex statements as well as the simpler form of statements handled by the methodsexecuteQuery
andexecuteUpdate
.The
execute
method returns aboolean
to indicate the form of the first result. You must call either the methodgetResultSet
orgetUpdateCount
to retrieve the result; you must callgetMoreResults
to move to any subsequent result(s).HSQLDB-Specific Information:
Including 1.8.0, prepared statements do not generate multiple fetchable results.
In future versions, it will be possible that statements generate multiple fetchable results under certain conditions.
- Specified by:
execute
in interfacejava.sql.PreparedStatement
- Returns:
true
if the first result is aResultSet
object;false
if the first result is an update count or there is no result- Throws:
java.sql.SQLException
- if a database access error occurs or an argument is supplied to this method- See Also:
jdbcStatement.execute(java.lang.String)
,jdbcStatement.getResultSet()
,jdbcStatement.getUpdateCount()
,jdbcStatement.getMoreResults()
-
executeQuery
public java.sql.ResultSet executeQuery() throws java.sql.SQLException
Executes the SQL query in thisPreparedStatement
object and returns theResultSet
object generated by the query.- Specified by:
executeQuery
in interfacejava.sql.PreparedStatement
- Returns:
- a
ResultSet
object that contains the data produced by the query; nevernull
- Throws:
java.sql.SQLException
- if a database access error occurs or the SQL statement does not return aResultSet
object
-
executeUpdate
public int executeUpdate() throws java.sql.SQLException
Executes the SQL statement in thisPreparedStatement
object, which must be an SQLINSERT
,UPDATE
orDELETE
statement; or an SQL statement that returns nothing, such as a DDL statement.- Specified by:
executeUpdate
in interfacejava.sql.PreparedStatement
- Returns:
- either (1) the row count for
INSERT
,UPDATE
, orDELETE
statements or (2) 0 for SQL statements that return nothing - Throws:
java.sql.SQLException
- if a database access error occurs or the SQL statement returns aResultSet
object
-
executeBatch
public int[] executeBatch() throws java.sql.SQLException
Submits a batch of commands to the database for execution and if all commands execute successfully, returns an array of update counts. Theint
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 methodexecuteBatch
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 unknownIf 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 methodBatchUpdateException.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.
- Specified by:
executeBatch
in interfacejava.sql.Statement
- Overrides:
executeBatch
in classjdbcStatement
- 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.
- Throws:
java.sql.SQLException
- if a database access error occurs or the driver does not support batch statements. ThrowsBatchUpdateException
(a subclass ofjava.sql.SQLException
) if one of the commands sent to the database fails to execute properly or attempts to return a result set.- Since:
- JDK 1.3 (JDK 1.1.x developers: read the new overview for jdbcStatement)
-
setNull
public void setNull(int paramIndex, int sqlType) throws java.sql.SQLException
Sets the designated parameter to SQLNULL
.Note: You must specify the parameter's SQL type.
HSQLDB-Specific Information:
HSQLDB ignores the sqlType argument.
- Specified by:
setNull
in interfacejava.sql.PreparedStatement
- Parameters:
paramIndex
- the first parameter is 1, the second is 2, ...sqlType
- the SQL type code defined injava.sql.Types
- Throws:
java.sql.SQLException
- if a database access error occurs
-
setBoolean
public void setBoolean(int parameterIndex, boolean x) throws java.sql.SQLException
Sets the designated parameter to the given Javaboolean
value. The driver converts this to an SQLBIT
value when it sends it to the database.HSQLDB-Specific Information:
Since 1.7.2, HSQLDB uses the BOOLEAN type instead of BIT, as per SQL 200n (SQL 3).
- Specified by:
setBoolean
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter value- Throws:
java.sql.SQLException
- if a database access error occurs
-
setByte
public void setByte(int parameterIndex, byte x) throws java.sql.SQLException
Sets the designated parameter to the given Javabyte
value. The driver converts this to an SQLTINYINT
value when it sends it to the database.- Specified by:
setByte
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter value- Throws:
java.sql.SQLException
- if a database access error occurs
-
setShort
public void setShort(int parameterIndex, short x) throws java.sql.SQLException
Sets the designated parameter to the given Javashort
value. The driver converts this to an SQLSMALLINT
value when it sends it to the database.- Specified by:
setShort
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter value- Throws:
java.sql.SQLException
- if a database access error occurs
-
setInt
public void setInt(int parameterIndex, int x) throws java.sql.SQLException
Sets the designated parameter to the given Javaint
value. The driver converts this to an SQLINTEGER
value when it sends it to the database.- Specified by:
setInt
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter value- Throws:
java.sql.SQLException
- if a database access error occurs
-
setLong
public void setLong(int parameterIndex, long x) throws java.sql.SQLException
Sets the designated parameter to the given Javalong
value. The driver converts this to an SQLBIGINT
value when it sends it to the database.- Specified by:
setLong
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter value- Throws:
java.sql.SQLException
- if a database access error occurs
-
setFloat
public void setFloat(int parameterIndex, float x) throws java.sql.SQLException
Sets the designated parameter to the given Javafloat
value. The driver converts this to an SQLFLOAT
value when it sends it to the database.HSQLDB-Specific Information:
Since 1.7.1, HSQLDB handles Java positive/negative Infinity and NaN
float
values consistent with the Java Language Specification; these special values are now correctly stored to and retrieved from the database.- Specified by:
setFloat
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter value- Throws:
java.sql.SQLException
- if a database access error occurs
-
setDouble
public void setDouble(int parameterIndex, double x) throws java.sql.SQLException
Sets the designated parameter to the given Javadouble
value. The driver converts this to an SQLDOUBLE
value when it sends it to the database.HSQLDB-Specific Information:
Since 1.7.1, HSQLDB handles Java positive/negative Infinity and NaN
double
values consistent with the Java Language Specification; these special values are now correctly stored to and retrieved from the database.- Specified by:
setDouble
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter value- Throws:
java.sql.SQLException
- if a database access error occurs
-
setBigDecimal
public void setBigDecimal(int parameterIndex, java.math.BigDecimal x) throws java.sql.SQLException
Sets the designated parameter to the givenjava.math.BigDecimal
value. The driver converts this to an SQLNUMERIC
value when it sends it to the database.- Specified by:
setBigDecimal
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter value- Throws:
java.sql.SQLException
- if a database access error occurs
-
setString
public void setString(int parameterIndex, java.lang.String x) throws java.sql.SQLException
Sets the designated parameter to the given JavaString
value. The driver converts this to an SQLVARCHAR
orLONGVARCHAR
value (depending on the argument's size relative to the driver's limits onVARCHAR
values) when it sends it to the database.HSQLDB-Specific Information:
Including 1.7.2, HSQLDB stores all XXXCHAR values as java.lang.String objects; there is no appreciable difference between CHAR, VARCHAR and LONGVARCHAR.
- Specified by:
setString
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter value- Throws:
java.sql.SQLException
- if a database access error occurs
-
setBytes
public void setBytes(int paramIndex, byte[] x) throws java.sql.SQLException
Sets the designated parameter to the given Java array of bytes. The driver converts this to an SQLVARBINARY
orLONGVARBINARY
(depending on the argument's size relative to the driver's limits onVARBINARY
values) when it sends it to the database.HSQLDB-Specific Information:
Including 1.7.2, HSQLDB stores all XXXBINARY values the same way; there is no appreciable difference between BINARY, VARBINARY and LONGVARBINARY.
- Specified by:
setBytes
in interfacejava.sql.PreparedStatement
- Parameters:
paramIndex
- the first parameter is 1, the second is 2, ...x
- the parameter value- Throws:
java.sql.SQLException
- if a database access error occurs
-
setDate
public void setDate(int parameterIndex, java.sql.Date x) throws java.sql.SQLException
Sets the designated parameter to the givenjava.sql.Date
value. The driver converts this to an SQLDATE
value when it sends it to the database.- Specified by:
setDate
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter value- Throws:
java.sql.SQLException
- if a database access error occurs
-
setTime
public void setTime(int parameterIndex, java.sql.Time x) throws java.sql.SQLException
Sets the designated parameter to the givenjava.sql.Time
value. The driver converts this to an SQLTIME
value when it sends it to the database.- Specified by:
setTime
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter value- Throws:
java.sql.SQLException
- if a database access error occurs
-
setTimestamp
public void setTimestamp(int parameterIndex, java.sql.Timestamp x) throws java.sql.SQLException
Sets the designated parameter to the givenjava.sql.Timestamp
value. The driver converts this to an SQLTIMESTAMP
value when it sends it to the database.- Specified by:
setTimestamp
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter value- Throws:
java.sql.SQLException
- if a database access error occurs
-
setAsciiStream
public void setAsciiStream(int parameterIndex, java.io.InputStream x, int length) throws java.sql.SQLException
Sets the designated parameter to the given input stream, which will have the specified number of bytes. When a very large ASCII value is input to aLONGVARCHAR
parameter, it may be more practical to send it via ajava.io.InputStream
. Data will be read from the stream as needed until end-of-file is reached. The JDBC driver will do any necessary conversion from ASCII to the database char format.Note: This stream object can either be a standard Java stream object or your own subclass that implements the standard interface.
HSQLDB-Specific Information:
This method uses the default platform character encoding to convert bytes from the stream into the characters of a String. In the future this is likely to change to always treat the stream as ASCII.
Before HSQLDB 1.7.0,
setAsciiStream
andsetUnicodeStream
were identical.- Specified by:
setAsciiStream
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the Java input stream that contains the ASCII parameter valuelength
- the number of bytes in the stream- Throws:
java.sql.SQLException
- if a database access error occurs
-
setUnicodeStream
public void setUnicodeStream(int parameterIndex, java.io.InputStream x, int length) throws java.sql.SQLException
Deprecated.Sun does not include a reason, but presumably this is because setCharacterStream is now preferedSets the designated parameter to the given input stream, which will have the specified number of bytes. A Unicode character has two bytes, with the first byte being the high byte, and the second being the low byte. When a very large Unicode value is input to aLONGVARCHAR
parameter, it may be more practical to send it via ajava.io.InputStream
object. The data will be read from the stream as needed until end-of-file is reached. The JDBC driver will do any necessary conversion from Unicode to the database char format.Note: This stream object can either be a standard Java stream object or your own subclass that implements the standard interface.
HSQLDB-Specific Information:
Since 1.7.0, this method complies with behavior as defined by the JDBC3 specification.
- Specified by:
setUnicodeStream
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- ajava.io.InputStream
object that contains the Unicode parameter value as two-byte Unicode characterslength
- the number of bytes in the stream- Throws:
java.sql.SQLException
- if a database access error occurs
-
setBinaryStream
public void setBinaryStream(int parameterIndex, java.io.InputStream x, int length) throws java.sql.SQLException
Sets the designated parameter to the given input stream, which will have the specified number of bytes. When a very large binary value is input to aLONGVARBINARY
parameter, it may be more practical to send it via ajava.io.InputStream
object. The data will be read from the stream as needed until end-of-file is reached.Note: This stream object can either be a standard Java stream object or your own subclass that implements the standard interface.
HSQLDB-Specific Information:
Since 1.7.2, this method works according to the standard.
- Specified by:
setBinaryStream
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the java input stream which contains the binary parameter valuelength
- the number of bytes in the stream- Throws:
java.sql.SQLException
- if a database access error occurs
-
clearParameters
public void clearParameters() throws java.sql.SQLException
Clears the current parameter values immediately.In general, parameter values remain in force for repeated use of a statement. Setting a parameter value automatically clears its previous value. However, in some cases it is useful to immediately release the resources used by the current parameter values; this can be done by calling the method
clearParameters
.- Specified by:
clearParameters
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
- if a database access error occurs
-
setObject
public void setObject(int parameterIndex, java.lang.Object x, int targetSqlType, int scale) throws java.sql.SQLException
Sets the value of the designated parameter with the given object.The second argument must be an object type; for integral values, the
java.lang
equivalent objects should be used.The given Java object will be converted to the given targetSqlType before being sent to the database. If the object has a custom mapping (is of a class implementing the interface
SQLData
), the JDBC driver should call the methodSQLData.writeSQL
to write it to the SQL data stream. If, on the other hand, the object is of a class implementingRef
,Blob
,Clob
,Struct
, orArray
, the driver should pass it to the database as a value of the corresponding SQL type.Note that this method may be used to pass database-specific abstract data types.
HSQLDB-Specific Information:
Inculding 1.7.1,this method was identical to
setObject(int, Object, int)
. That is, this method simply called setObject(int, Object, int), ignoring the scale specification.Since 1.7.2, this method supports the conversions listed in the conversion table B-5 of the JDBC 3 specification. The scale argument is not used.
- Specified by:
setObject
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the object containing the input parameter valuetargetSqlType
- the SQL type (as defined in java.sql.Types) to be sent to the database. The scale argument may further qualify this type.scale
- for java.sql.Types.DECIMAL or java.sql.Types.NUMERIC types, this is the number of digits after the decimal point. For all other types, this value will be ignored.Up to and including HSQLDB 1.7.0, this parameter is ignored.
- Throws:
java.sql.SQLException
- if a database access error occurs- See Also:
Types
,setObject(int,Object,int)
-
setObject
public void setObject(int parameterIndex, java.lang.Object x, int targetSqlType) throws java.sql.SQLException
Sets the value of the designated parameter with the given object. This method is like the methodsetObject
above, except that it assumes a scale of zero.HSQLDB-Specific Information:
Since 1.7.2, this method supports conversions listed in the conversion table B-5 of the JDBC 3 specification.
- Specified by:
setObject
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the object containing the input parameter valuetargetSqlType
- the SQL type (as defined in java.sql.Types) to be sent to the database- Throws:
java.sql.SQLException
- if a database access error occurs- See Also:
setObject(int,Object)
-
setObject
public void setObject(int parameterIndex, java.lang.Object x) throws java.sql.SQLException
Sets the value of the designated parameter using the given object.The second parameter must be of type
Object
; therefore, thejava.lang
equivalent objects should be used for built-in types.The JDBC specification specifies a standard mapping from Java
Object
types to SQL types. The given argument will be converted to the corresponding SQL type before being sent to the database.Note that this method may be used to pass datatabase- specific abstract data types, by using a driver-specific Java type. If the object is of a class implementing the interface
SQLData
, the JDBC driver should call the methodSQLData.writeSQL
to write it to the SQL data stream. If, on the other hand, the object is of a class implementingRef
,Blob
,Clob
,Struct
, orArray
, the driver should pass it to the database as a value of the corresponding SQL type.This method throws an exception if there is an ambiguity, for example, if the object is of a class implementing more than one of the interfaces named above.
HSQLDB-Specific Information:
Since 1.7.2, this method supports conversions listed in the conversion table B-5 of the JDBC 3 specification.
- Specified by:
setObject
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the object containing the input parameter value- Throws:
java.sql.SQLException
- if a database access error occurs or the type of the given object is ambiguous
-
addBatch
public void addBatch() throws java.sql.SQLException
Adds a set of parameters to thisPreparedStatement
object's batch of commands.HSQLDB-Specific Information:
Since 1.7.2, this feature is supported.
- Specified by:
addBatch
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
- if a database access error occurs- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
- See Also:
jdbcStatement.addBatch(java.lang.String)
-
setCharacterStream
public void setCharacterStream(int parameterIndex, java.io.Reader reader, int length) throws java.sql.SQLException
Sets the designated parameter to the givenReader
object, which is the given number of characters long. When a very large UNICODE value is input to aLONGVARCHAR
parameter, it may be more practical to send it via ajava.io.Reader
object. The data will be read from the stream as needed until end-of-file is reached. The JDBC driver will do any necessary conversion from UNICODE to the database char format.Note: This stream object can either be a standard Java stream object or your own subclass that implements the standard interface.
HSQLDB-Specific Information:
HSQLDB stores CHARACTER and related SQL types as Unicode so this method does not perform any conversion.
- Specified by:
setCharacterStream
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...reader
- thejava.io.Reader
object that contains the Unicode datalength
- the number of characters in the stream- Throws:
java.sql.SQLException
- if a database access error occurs- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
-
setRef
public void setRef(int i, java.sql.Ref x) throws java.sql.SQLException
Sets the designated parameter to the givenREF(<structured-type>)
value. The driver converts this to an SQLREF
value when it sends it to the database.HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support the SQL REF type. Calling this method throws an exception.
- Specified by:
setRef
in interfacejava.sql.PreparedStatement
- Parameters:
i
- the first parameter is 1, the second is 2, ...x
- an SQLREF
value- Throws:
java.sql.SQLException
- if a database access error occurs- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
-
setBlob
public void setBlob(int i, java.sql.Blob x) throws java.sql.SQLException
Sets the designated parameter to the givenBlob
object. The driver converts this to an SQLBLOB
value when it sends it to the database.HSQLDB-Specific Information:
Previous to 1.7.2, this feature was not supported.
Since 1.7.2, setBlob is supported. With 1.7.2, setting Blob objects is limited to those of length less than or equal to Integer.MAX_VALUE. In 1.7.2, setBlob(i,x) is roughly equivalent (null and length handling not shown) to:
setBinaryStream(i, x.getBinaryStream(), (int) x.length());
- Specified by:
setBlob
in interfacejava.sql.PreparedStatement
- Parameters:
i
- the first parameter is 1, the second is 2, ...x
- aBlob
object that maps an SQLBLOB
value- Throws:
java.sql.SQLException
- if a database access error occurs- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
-
setClob
public void setClob(int i, java.sql.Clob x) throws java.sql.SQLException
Sets the designated parameter to the givenClob
object. The driver converts this to an SQLCLOB
value when it sends it to the database.HSQLDB-Specific Information:
Previous to 1.7.2, this feature was not supported.
Since 1.7.2, setClob is supported. With 1.7.2, setting Blob objects is limited to those of length less than or equal to Integer.MAX_VALUE. In 1.7.2, setClob(i,x) is rougly equivalent (null and length handling not shown) to:
setCharacterStream(i, x.getCharacterStream(), (int) x.length());
- Specified by:
setClob
in interfacejava.sql.PreparedStatement
- Parameters:
i
- the first parameter is 1, the second is 2, ...x
- aClob
object that maps an SQLCLOB
value- Throws:
java.sql.SQLException
- if a database access error occurs- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
-
setArray
public void setArray(int i, java.sql.Array x) throws java.sql.SQLException
Sets the designated parameter to the givenArray
object. The driver converts this to an SQLARRAY
value when it sends it to the database.HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support the SQL ARRAY type. Calling this method throws an exception.
- Specified by:
setArray
in interfacejava.sql.PreparedStatement
- Parameters:
i
- the first parameter is 1, the second is 2, ...x
- anArray
object that maps an SQLARRAY
value- Throws:
java.sql.SQLException
- if a database access error occurs- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
-
getMetaData
public java.sql.ResultSetMetaData getMetaData() throws java.sql.SQLException
Retrieves aResultSetMetaData
object that contains information about the columns of theResultSet
object that will be returned when thisPreparedStatement
object is executed.Because a
PreparedStatement
object is precompiled, it is possible to know about theResultSet
object that it will return without having to execute it. Consequently, it is possible to invoke the methodgetMetaData
on aPreparedStatement
object rather than waiting to execute it and then invoking theResultSet.getMetaData
method on theResultSet
object that is returned.NOTE: Using this method may be expensive for some drivers due to the lack of underlying DBMS support.
HSQLDB-Specific Information:
Since 1.7.2, this feature is supported. If the statement generates an update count, then null is returned.
- Specified by:
getMetaData
in interfacejava.sql.PreparedStatement
- Returns:
- the description of a
ResultSet
object's columns ornull
if the driver cannot return aResultSetMetaData
object - Throws:
java.sql.SQLException
- if a database access error occurs- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
-
setDate
public void setDate(int parameterIndex, java.sql.Date x, java.util.Calendar cal) throws java.sql.SQLException
Sets the designated parameter to the givenjava.sql.Date
value, using the givenCalendar
object. The driver uses theCalendar
object to construct an SQLDATE
value,which the driver then sends to the database. With a aCalendar
object, the driver can calculate the date taking into account a custom timezone. If noCalendar
object is specified, the driver uses the default timezone, which is that of the virtual machine running the application.- Specified by:
setDate
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter valuecal
- theCalendar
object the driver will use to construct the date- Throws:
java.sql.SQLException
- if a database access error occurs- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
-
setTime
public void setTime(int parameterIndex, java.sql.Time x, java.util.Calendar cal) throws java.sql.SQLException
Sets the designated parameter to the givenjava.sql.Time
value, using the givenCalendar
object. The driver uses theCalendar
object to construct an SQLTIME
value, which the driver then sends to the database. With a aCalendar
object, the driver can calculate the time taking into account a custom timezone. If noCalendar
object is specified, the driver uses the default timezone, which is that of the virtual machine running the application.- Specified by:
setTime
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter valuecal
- theCalendar
object the driver will use to construct the time- Throws:
java.sql.SQLException
- if a database access error occurs- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
-
setTimestamp
public void setTimestamp(int parameterIndex, java.sql.Timestamp x, java.util.Calendar cal) throws java.sql.SQLException
Sets the designated parameter to the givenjava.sql.Timestamp
value, using the givenCalendar
object. The driver uses theCalendar
object to construct an SQLTIMESTAMP
value, which the driver then sends to the database. With aCalendar
object, the driver can calculate the timestamp taking into account a custom timezone. If noCalendar
object is specified, the driver uses the default timezone, which is that of the virtual machine running the application.- Specified by:
setTimestamp
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- the parameter valuecal
- theCalendar
object the driver will use to construct the timestamp- Throws:
java.sql.SQLException
- if a database access error occurs- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
-
setNull
public void setNull(int paramIndex, int sqlType, java.lang.String typeName) throws java.sql.SQLException
Sets the designated parameter to SQLNULL
. This version of the methodsetNull
should be used for user-defined types and REF type parameters. Examples of user-defined types include: STRUCT, DISTINCT, JAVA_OBJECT, and named array types.Note: To be portable, applications must give the SQL type code and the fully-qualified SQL type name when specifying a NULL user-defined or REF parameter. In the case of a user-defined type the name is the type name of the parameter itself. For a REF parameter, the name is the type name of the referenced type. If a JDBC driver does not need the type code or type name information, it may ignore it. Although it is intended for user-defined and Ref parameters, this method may be used to set a null parameter of any JDBC type. If the parameter does not have a user-defined or REF type, the given typeName is ignored.
HSQLDB-Specific Information:
HSQLDB ignores the sqlType and typeName arguments.
- Specified by:
setNull
in interfacejava.sql.PreparedStatement
- Parameters:
paramIndex
- the first parameter is 1, the second is 2, ...sqlType
- a value fromjava.sql.Types
typeName
- the fully-qualified name of an SQL user-defined type; ignored if the parameter is not a user-defined type or REF- Throws:
java.sql.SQLException
- if a database access error occurs- Since:
- JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
-
setURL
public void setURL(int parameterIndex, java.net.URL x) throws java.sql.SQLException
Sets the designated parameter to the givenjava.net.URL
value. The driver converts this to an SQLDATALINK
value when it sends it to the database.HSQLDB-Specific Information:
HSQLDB 1.7.2 does not support the DATALINK SQL type for which this method is intended. Calling this method throws an exception.
- Specified by:
setURL
in interfacejava.sql.PreparedStatement
- Parameters:
parameterIndex
- the first parameter is 1, the second is 2, ...x
- thejava.net.URL
object to be set- Throws:
java.sql.SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQL 1.7.0
-
getParameterMetaData
public java.sql.ParameterMetaData getParameterMetaData() throws java.sql.SQLException
Retrieves the number, types and properties of thisPreparedStatement
object's parameters.HSQLDB-Specific Information:
Since 1.7.2, this feature is supported.
- Specified by:
getParameterMetaData
in interfacejava.sql.PreparedStatement
- Returns:
- a
ParameterMetaData
object that contains information about the number, types and properties of thisPreparedStatement
object's parameters - Throws:
java.sql.SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQL 1.7.0
- See Also:
ParameterMetaData
-
addBatch
public void addBatch(java.lang.String sql) throws java.sql.SQLException
This method should always throw if called for a PreparedStatement or CallableStatment.- Specified by:
addBatch
in interfacejava.sql.Statement
- Overrides:
addBatch
in classjdbcStatement
- Parameters:
sql
- ignored- Throws:
java.sql.SQLException
- always- See Also:
jdbcStatement.executeBatch()
-
executeQuery
public java.sql.ResultSet executeQuery(java.lang.String sql) throws java.sql.SQLException
This method should always throw if called for a PreparedStatement or CallableStatment.- Specified by:
executeQuery
in interfacejava.sql.Statement
- Overrides:
executeQuery
in classjdbcStatement
- Parameters:
sql
- ignored- Returns:
- nothing
- Throws:
java.sql.SQLException
- always
-
execute
public boolean execute(java.lang.String sql) throws java.sql.SQLException
This method should always throw if called for a PreparedStatement or CallableStatment.- Specified by:
execute
in interfacejava.sql.Statement
- Overrides:
execute
in classjdbcStatement
- Parameters:
sql
- ignored- Returns:
- nothing
- Throws:
java.sql.SQLException
- always- See Also:
jdbcStatement.getResultSet()
,jdbcStatement.getUpdateCount()
,jdbcStatement.getMoreResults()
-
executeUpdate
public int executeUpdate(java.lang.String sql) throws java.sql.SQLException
This method should always throw if called for a PreparedStatement or CallableStatment.- Specified by:
executeUpdate
in interfacejava.sql.Statement
- Overrides:
executeUpdate
in classjdbcStatement
- Parameters:
sql
- ignored- Returns:
- nothing
- Throws:
java.sql.SQLException
- always
-
close
public void close() throws java.sql.SQLException
Does the specialized work required to free this object's resources and that of it's parent class.- Specified by:
close
in interfacejava.lang.AutoCloseable
- Specified by:
close
in interfacejava.sql.Statement
- Overrides:
close
in classjdbcStatement
- Throws:
java.sql.SQLException
- if a database access error occurs
-
toString
public java.lang.String toString()
Retrieves a String representation of this object.The representation is of the form:
class-name@hash[sql=[char-sequence], parameters=[p1, ...pi, ...pn]]
p1, ...pi, ...pn are the String representations of the currently set parameter values that will be used with the non-batch execution methods.
- Overrides:
toString
in classjava.lang.Object
- Returns:
- a String representation of this object
-
setPoolable
public void setPoolable(boolean poolable) throws java.sql.SQLException
- Specified by:
setPoolable
in interfacejava.sql.Statement
- Overrides:
setPoolable
in classjdbcStatement
- Throws:
java.sql.SQLException
-
isPoolable
public boolean isPoolable() throws java.sql.SQLException
- Specified by:
isPoolable
in interfacejava.sql.Statement
- Overrides:
isPoolable
in classjdbcStatement
- Throws:
java.sql.SQLException
-
unwrap
public <T> T unwrap(java.lang.Class<T> iface) throws java.sql.SQLException
- Specified by:
unwrap
in interfacejava.sql.Wrapper
- Overrides:
unwrap
in classjdbcStatement
- Throws:
java.sql.SQLException
-
isWrapperFor
public boolean isWrapperFor(java.lang.Class<?> iface) throws java.sql.SQLException
- Specified by:
isWrapperFor
in interfacejava.sql.Wrapper
- Overrides:
isWrapperFor
in classjdbcStatement
- Throws:
java.sql.SQLException
-
setRowId
public void setRowId(int parameterIndex, java.sql.RowId x) throws java.sql.SQLException
- Specified by:
setRowId
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setNString
public void setNString(int parameterIndex, java.lang.String value) throws java.sql.SQLException
- Specified by:
setNString
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setNCharacterStream
public void setNCharacterStream(int parameterIndex, java.io.Reader value, long length) throws java.sql.SQLException
- Specified by:
setNCharacterStream
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setNClob
public void setNClob(int parameterIndex, java.sql.NClob value) throws java.sql.SQLException
- Specified by:
setNClob
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setClob
public void setClob(int parameterIndex, java.io.Reader reader, long length) throws java.sql.SQLException
- Specified by:
setClob
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setBlob
public void setBlob(int parameterIndex, java.io.InputStream inputStream, long length) throws java.sql.SQLException
- Specified by:
setBlob
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setNClob
public void setNClob(int parameterIndex, java.io.Reader reader, long length) throws java.sql.SQLException
- Specified by:
setNClob
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setSQLXML
public void setSQLXML(int parameterIndex, java.sql.SQLXML xmlObject) throws java.sql.SQLException
- Specified by:
setSQLXML
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setAsciiStream
public void setAsciiStream(int parameterIndex, java.io.InputStream x, long length) throws java.sql.SQLException
- Specified by:
setAsciiStream
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setBinaryStream
public void setBinaryStream(int parameterIndex, java.io.InputStream x, long length) throws java.sql.SQLException
- Specified by:
setBinaryStream
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setCharacterStream
public void setCharacterStream(int parameterIndex, java.io.Reader reader, long length) throws java.sql.SQLException
- Specified by:
setCharacterStream
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setAsciiStream
public void setAsciiStream(int parameterIndex, java.io.InputStream x) throws java.sql.SQLException
- Specified by:
setAsciiStream
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setBinaryStream
public void setBinaryStream(int parameterIndex, java.io.InputStream x) throws java.sql.SQLException
- Specified by:
setBinaryStream
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setCharacterStream
public void setCharacterStream(int parameterIndex, java.io.Reader reader) throws java.sql.SQLException
- Specified by:
setCharacterStream
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setNCharacterStream
public void setNCharacterStream(int parameterIndex, java.io.Reader value) throws java.sql.SQLException
- Specified by:
setNCharacterStream
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setClob
public void setClob(int parameterIndex, java.io.Reader reader) throws java.sql.SQLException
- Specified by:
setClob
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setBlob
public void setBlob(int parameterIndex, java.io.InputStream inputStream) throws java.sql.SQLException
- Specified by:
setBlob
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
setNClob
public void setNClob(int parameterIndex, java.io.Reader reader) throws java.sql.SQLException
- Specified by:
setNClob
in interfacejava.sql.PreparedStatement
- Throws:
java.sql.SQLException
-
-