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
PreparedStatementobject. 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 methodsetIntshould be used.If arbitrary parameter type conversions are required, the method
setObjectshould be used with a target SQL type.In the following example of setting a parameter,
conrepresents 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
intvalues that are defined only in the JDBC 2 or greater version ofResultSetinterface. 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
ResultSetvalues 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 voidaddBatch()Adds a set of parameters to thisPreparedStatementobject's batch of commands.voidaddBatch(java.lang.String sql)This method should always throw if called for a PreparedStatement or CallableStatment.voidclearParameters()Clears the current parameter values immediately.voidclose()Does the specialized work required to free this object's resources and that of it's parent class.booleanexecute()Executes the SQL statement in thisPreparedStatementobject, which may be any kind of SQL statement.booleanexecute(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.ResultSetexecuteQuery()Executes the SQL query in thisPreparedStatementobject and returns theResultSetobject generated by the query.java.sql.ResultSetexecuteQuery(java.lang.String sql)This method should always throw if called for a PreparedStatement or CallableStatment.intexecuteUpdate()Executes the SQL statement in thisPreparedStatementobject, which must be an SQLINSERT,UPDATEorDELETEstatement; or an SQL statement that returns nothing, such as a DDL statement.intexecuteUpdate(java.lang.String sql)This method should always throw if called for a PreparedStatement or CallableStatment.java.sql.ResultSetMetaDatagetMetaData()Retrieves aResultSetMetaDataobject that contains information about the columns of theResultSetobject that will be returned when thisPreparedStatementobject is executed.java.sql.ParameterMetaDatagetParameterMetaData()Retrieves the number, types and properties of thisPreparedStatementobject's parameters.booleanisPoolable()booleanisWrapperFor(java.lang.Class<?> iface)voidsetArray(int i, java.sql.Array x)Sets the designated parameter to the givenArrayobject.voidsetAsciiStream(int parameterIndex, java.io.InputStream x)voidsetAsciiStream(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.voidsetAsciiStream(int parameterIndex, java.io.InputStream x, long length)voidsetBigDecimal(int parameterIndex, java.math.BigDecimal x)Sets the designated parameter to the givenjava.math.BigDecimalvalue.voidsetBinaryStream(int parameterIndex, java.io.InputStream x)voidsetBinaryStream(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.voidsetBinaryStream(int parameterIndex, java.io.InputStream x, long length)voidsetBlob(int parameterIndex, java.io.InputStream inputStream)voidsetBlob(int parameterIndex, java.io.InputStream inputStream, long length)voidsetBlob(int i, java.sql.Blob x)Sets the designated parameter to the givenBlobobject.voidsetBoolean(int parameterIndex, boolean x)Sets the designated parameter to the given Javabooleanvalue.voidsetByte(int parameterIndex, byte x)Sets the designated parameter to the given Javabytevalue.voidsetBytes(int paramIndex, byte[] x)Sets the designated parameter to the given Java array of bytes.voidsetCharacterStream(int parameterIndex, java.io.Reader reader)voidsetCharacterStream(int parameterIndex, java.io.Reader reader, int length)Sets the designated parameter to the givenReaderobject, which is the given number of characters long.voidsetCharacterStream(int parameterIndex, java.io.Reader reader, long length)voidsetClob(int parameterIndex, java.io.Reader reader)voidsetClob(int parameterIndex, java.io.Reader reader, long length)voidsetClob(int i, java.sql.Clob x)Sets the designated parameter to the givenClobobject.voidsetDate(int parameterIndex, java.sql.Date x)Sets the designated parameter to the givenjava.sql.Datevalue.voidsetDate(int parameterIndex, java.sql.Date x, java.util.Calendar cal)Sets the designated parameter to the givenjava.sql.Datevalue, using the givenCalendarobject.voidsetDouble(int parameterIndex, double x)Sets the designated parameter to the given Javadoublevalue.voidsetEscapeProcessing(boolean enable)Sets escape processing on or off.voidsetFloat(int parameterIndex, float x)Sets the designated parameter to the given Javafloatvalue.voidsetInt(int parameterIndex, int x)Sets the designated parameter to the given Javaintvalue.voidsetLong(int parameterIndex, long x)Sets the designated parameter to the given Javalongvalue.voidsetNCharacterStream(int parameterIndex, java.io.Reader value)voidsetNCharacterStream(int parameterIndex, java.io.Reader value, long length)voidsetNClob(int parameterIndex, java.io.Reader reader)voidsetNClob(int parameterIndex, java.io.Reader reader, long length)voidsetNClob(int parameterIndex, java.sql.NClob value)voidsetNString(int parameterIndex, java.lang.String value)voidsetNull(int paramIndex, int sqlType)Sets the designated parameter to SQLNULL.voidsetNull(int paramIndex, int sqlType, java.lang.String typeName)Sets the designated parameter to SQLNULL.voidsetObject(int parameterIndex, java.lang.Object x)Sets the value of the designated parameter using the given object.voidsetObject(int parameterIndex, java.lang.Object x, int targetSqlType)Sets the value of the designated parameter with the given object.voidsetObject(int parameterIndex, java.lang.Object x, int targetSqlType, int scale)Sets the value of the designated parameter with the given object.voidsetPoolable(boolean poolable)voidsetRef(int i, java.sql.Ref x)Sets the designated parameter to the givenREF(<structured-type>)value.voidsetRowId(int parameterIndex, java.sql.RowId x)voidsetShort(int parameterIndex, short x)Sets the designated parameter to the given Javashortvalue.voidsetSQLXML(int parameterIndex, java.sql.SQLXML xmlObject)voidsetString(int parameterIndex, java.lang.String x)Sets the designated parameter to the given JavaStringvalue.voidsetTime(int parameterIndex, java.sql.Time x)Sets the designated parameter to the givenjava.sql.Timevalue.voidsetTime(int parameterIndex, java.sql.Time x, java.util.Calendar cal)Sets the designated parameter to the givenjava.sql.Timevalue, using the givenCalendarobject.voidsetTimestamp(int parameterIndex, java.sql.Timestamp x)Sets the designated parameter to the givenjava.sql.Timestampvalue.voidsetTimestamp(int parameterIndex, java.sql.Timestamp x, java.util.Calendar cal)Sets the designated parameter to the givenjava.sql.Timestampvalue, using the givenCalendarobject.voidsetUnicodeStream(int parameterIndex, java.io.InputStream x, int length)Deprecated.Sun does not include a reason, but presumably this is because setCharacterStream is now preferedvoidsetURL(int parameterIndex, java.net.URL x)Sets the designated parameter to the givenjava.net.URLvalue.java.lang.StringtoString()Retrieves a String representation of this object.<T> Tunwrap(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.SQLExceptionSets 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:
setEscapeProcessingin interfacejava.sql.Statement- Overrides:
setEscapeProcessingin classjdbcStatement- Parameters:
enable-trueto enable escape processing;falseto disable it- Throws:
java.sql.SQLException- if a database access error occurs
-
execute
public boolean execute() throws java.sql.SQLExceptionExecutes the SQL statement in thisPreparedStatementobject, which may be any kind of SQL statement. Some prepared statements return multiple results; theexecutemethod handles these complex statements as well as the simpler form of statements handled by the methodsexecuteQueryandexecuteUpdate.The
executemethod returns abooleanto indicate the form of the first result. You must call either the methodgetResultSetorgetUpdateCountto retrieve the result; you must callgetMoreResultsto 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:
executein interfacejava.sql.PreparedStatement- Returns:
trueif the first result is aResultSetobject;falseif 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.SQLExceptionExecutes the SQL query in thisPreparedStatementobject and returns theResultSetobject generated by the query.- Specified by:
executeQueryin interfacejava.sql.PreparedStatement- Returns:
- a
ResultSetobject 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 aResultSetobject
-
executeUpdate
public int executeUpdate() throws java.sql.SQLExceptionExecutes the SQL statement in thisPreparedStatementobject, which must be an SQLINSERT,UPDATEorDELETEstatement; or an SQL statement that returns nothing, such as a DDL statement.- Specified by:
executeUpdatein interfacejava.sql.PreparedStatement- Returns:
- either (1) the row count for
INSERT,UPDATE, orDELETEstatements or (2) 0 for SQL statements that return nothing - Throws:
java.sql.SQLException- if a database access error occurs or the SQL statement returns aResultSetobject
-
executeBatch
public int[] executeBatch() throws java.sql.SQLExceptionSubmits a batch of commands to the database for execution and if all commands execute successfully, returns an array of update counts. Theintelements of the array that is returned are ordered to correspond to the commands in the batch, which are ordered according to the order in which they were added to the batch. The elements in the array returned by the methodexecuteBatchmay be one of the following:- A 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.getUpdateCountswill contain as many elements as there are commands in the batch, and at least one of the elements will be the following: - A value of
EXECUTE_FAILED-- indicates that the command failed to execute successfully and occurs only if a driver continues to process commands after a command 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
BatchUpdateExceptionobejct 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:
executeBatchin interfacejava.sql.Statement- Overrides:
executeBatchin 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.SQLExceptionSets the designated parameter to SQLNULL.Note: You must specify the parameter's SQL type.
HSQLDB-Specific Information:
HSQLDB ignores the sqlType argument.
- Specified by:
setNullin 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.SQLExceptionSets the designated parameter to the given Javabooleanvalue. The driver converts this to an SQLBITvalue 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:
setBooleanin 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.SQLExceptionSets the designated parameter to the given Javabytevalue. The driver converts this to an SQLTINYINTvalue when it sends it to the database.- Specified by:
setBytein 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.SQLExceptionSets the designated parameter to the given Javashortvalue. The driver converts this to an SQLSMALLINTvalue when it sends it to the database.- Specified by:
setShortin 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.SQLExceptionSets the designated parameter to the given Javaintvalue. The driver converts this to an SQLINTEGERvalue when it sends it to the database.- Specified by:
setIntin 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.SQLExceptionSets the designated parameter to the given Javalongvalue. The driver converts this to an SQLBIGINTvalue when it sends it to the database.- Specified by:
setLongin 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.SQLExceptionSets the designated parameter to the given Javafloatvalue. The driver converts this to an SQLFLOATvalue when it sends it to the database.HSQLDB-Specific Information:
Since 1.7.1, HSQLDB handles Java positive/negative Infinity and NaN
floatvalues consistent with the Java Language Specification; these special values are now correctly stored to and retrieved from the database.- Specified by:
setFloatin 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.SQLExceptionSets the designated parameter to the given Javadoublevalue. The driver converts this to an SQLDOUBLEvalue when it sends it to the database.HSQLDB-Specific Information:
Since 1.7.1, HSQLDB handles Java positive/negative Infinity and NaN
doublevalues consistent with the Java Language Specification; these special values are now correctly stored to and retrieved from the database.- Specified by:
setDoublein 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.SQLExceptionSets the designated parameter to the givenjava.math.BigDecimalvalue. The driver converts this to an SQLNUMERICvalue when it sends it to the database.- Specified by:
setBigDecimalin 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.SQLExceptionSets the designated parameter to the given JavaStringvalue. The driver converts this to an SQLVARCHARorLONGVARCHARvalue (depending on the argument's size relative to the driver's limits onVARCHARvalues) 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:
setStringin 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.SQLExceptionSets the designated parameter to the given Java array of bytes. The driver converts this to an SQLVARBINARYorLONGVARBINARY(depending on the argument's size relative to the driver's limits onVARBINARYvalues) 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:
setBytesin 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.SQLExceptionSets the designated parameter to the givenjava.sql.Datevalue. The driver converts this to an SQLDATEvalue when it sends it to the database.- Specified by:
setDatein 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.SQLExceptionSets the designated parameter to the givenjava.sql.Timevalue. The driver converts this to an SQLTIMEvalue when it sends it to the database.- Specified by:
setTimein 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.SQLExceptionSets the designated parameter to the givenjava.sql.Timestampvalue. The driver converts this to an SQLTIMESTAMPvalue when it sends it to the database.- Specified by:
setTimestampin 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.SQLExceptionSets 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 aLONGVARCHARparameter, 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,
setAsciiStreamandsetUnicodeStreamwere identical.- Specified by:
setAsciiStreamin 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.SQLExceptionDeprecated.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 aLONGVARCHARparameter, it may be more practical to send it via ajava.io.InputStreamobject. 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:
setUnicodeStreamin interfacejava.sql.PreparedStatement- Parameters:
parameterIndex- the first parameter is 1, the second is 2, ...x- ajava.io.InputStreamobject 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.SQLExceptionSets 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 aLONGVARBINARYparameter, it may be more practical to send it via ajava.io.InputStreamobject. 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:
setBinaryStreamin 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.SQLExceptionClears 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:
clearParametersin 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.SQLExceptionSets the value of the designated parameter with the given object.The second argument must be an object type; for integral values, the
java.langequivalent 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.writeSQLto 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:
setObjectin 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.SQLExceptionSets the value of the designated parameter with the given object. This method is like the methodsetObjectabove, 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:
setObjectin 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.SQLExceptionSets the value of the designated parameter using the given object.The second parameter must be of type
Object; therefore, thejava.langequivalent objects should be used for built-in types.The JDBC specification specifies a standard mapping from Java
Objecttypes 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.writeSQLto 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:
setObjectin 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.SQLExceptionAdds a set of parameters to thisPreparedStatementobject's batch of commands.HSQLDB-Specific Information:
Since 1.7.2, this feature is supported.
- Specified by:
addBatchin 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.SQLExceptionSets the designated parameter to the givenReaderobject, which is the given number of characters long. When a very large UNICODE value is input to aLONGVARCHARparameter, it may be more practical to send it via ajava.io.Readerobject. 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:
setCharacterStreamin interfacejava.sql.PreparedStatement- Parameters:
parameterIndex- the first parameter is 1, the second is 2, ...reader- thejava.io.Readerobject 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.SQLExceptionSets the designated parameter to the givenREF(<structured-type>)value. The driver converts this to an SQLREFvalue 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:
setRefin interfacejava.sql.PreparedStatement- Parameters:
i- the first parameter is 1, the second is 2, ...x- an SQLREFvalue- 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.SQLExceptionSets the designated parameter to the givenBlobobject. The driver converts this to an SQLBLOBvalue 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:
setBlobin interfacejava.sql.PreparedStatement- Parameters:
i- the first parameter is 1, the second is 2, ...x- aBlobobject that maps an SQLBLOBvalue- 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.SQLExceptionSets the designated parameter to the givenClobobject. The driver converts this to an SQLCLOBvalue 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:
setClobin interfacejava.sql.PreparedStatement- Parameters:
i- the first parameter is 1, the second is 2, ...x- aClobobject that maps an SQLCLOBvalue- 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.SQLExceptionSets the designated parameter to the givenArrayobject. The driver converts this to an SQLARRAYvalue 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:
setArrayin interfacejava.sql.PreparedStatement- Parameters:
i- the first parameter is 1, the second is 2, ...x- anArrayobject that maps an SQLARRAYvalue- 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.SQLExceptionRetrieves aResultSetMetaDataobject that contains information about the columns of theResultSetobject that will be returned when thisPreparedStatementobject is executed.Because a
PreparedStatementobject is precompiled, it is possible to know about theResultSetobject that it will return without having to execute it. Consequently, it is possible to invoke the methodgetMetaDataon aPreparedStatementobject rather than waiting to execute it and then invoking theResultSet.getMetaDatamethod on theResultSetobject 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:
getMetaDatain interfacejava.sql.PreparedStatement- Returns:
- the description of a
ResultSetobject's columns ornullif the driver cannot return aResultSetMetaDataobject - 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.SQLExceptionSets the designated parameter to the givenjava.sql.Datevalue, using the givenCalendarobject. The driver uses theCalendarobject to construct an SQLDATEvalue,which the driver then sends to the database. With a aCalendarobject, the driver can calculate the date taking into account a custom timezone. If noCalendarobject is specified, the driver uses the default timezone, which is that of the virtual machine running the application.- Specified by:
setDatein interfacejava.sql.PreparedStatement- Parameters:
parameterIndex- the first parameter is 1, the second is 2, ...x- the parameter valuecal- theCalendarobject 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.SQLExceptionSets the designated parameter to the givenjava.sql.Timevalue, using the givenCalendarobject. The driver uses theCalendarobject to construct an SQLTIMEvalue, which the driver then sends to the database. With a aCalendarobject, the driver can calculate the time taking into account a custom timezone. If noCalendarobject is specified, the driver uses the default timezone, which is that of the virtual machine running the application.- Specified by:
setTimein interfacejava.sql.PreparedStatement- Parameters:
parameterIndex- the first parameter is 1, the second is 2, ...x- the parameter valuecal- theCalendarobject 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.SQLExceptionSets the designated parameter to the givenjava.sql.Timestampvalue, using the givenCalendarobject. The driver uses theCalendarobject to construct an SQLTIMESTAMPvalue, which the driver then sends to the database. With aCalendarobject, the driver can calculate the timestamp taking into account a custom timezone. If noCalendarobject is specified, the driver uses the default timezone, which is that of the virtual machine running the application.- Specified by:
setTimestampin interfacejava.sql.PreparedStatement- Parameters:
parameterIndex- the first parameter is 1, the second is 2, ...x- the parameter valuecal- theCalendarobject 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.SQLExceptionSets the designated parameter to SQLNULL. This version of the methodsetNullshould 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:
setNullin interfacejava.sql.PreparedStatement- Parameters:
paramIndex- the first parameter is 1, the second is 2, ...sqlType- a value fromjava.sql.TypestypeName- 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.SQLExceptionSets the designated parameter to the givenjava.net.URLvalue. The driver converts this to an SQLDATALINKvalue 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:
setURLin interfacejava.sql.PreparedStatement- Parameters:
parameterIndex- the first parameter is 1, the second is 2, ...x- thejava.net.URLobject 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.SQLExceptionRetrieves the number, types and properties of thisPreparedStatementobject's parameters.HSQLDB-Specific Information:
Since 1.7.2, this feature is supported.
- Specified by:
getParameterMetaDatain interfacejava.sql.PreparedStatement- Returns:
- a
ParameterMetaDataobject that contains information about the number, types and properties of thisPreparedStatementobject'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.SQLExceptionThis method should always throw if called for a PreparedStatement or CallableStatment.- Specified by:
addBatchin interfacejava.sql.Statement- Overrides:
addBatchin 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.SQLExceptionThis method should always throw if called for a PreparedStatement or CallableStatment.- Specified by:
executeQueryin interfacejava.sql.Statement- Overrides:
executeQueryin classjdbcStatement- Parameters:
sql- ignored- Returns:
- nothing
- Throws:
java.sql.SQLException- always
-
execute
public boolean execute(java.lang.String sql) throws java.sql.SQLExceptionThis method should always throw if called for a PreparedStatement or CallableStatment.- Specified by:
executein interfacejava.sql.Statement- Overrides:
executein 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.SQLExceptionThis method should always throw if called for a PreparedStatement or CallableStatment.- Specified by:
executeUpdatein interfacejava.sql.Statement- Overrides:
executeUpdatein classjdbcStatement- Parameters:
sql- ignored- Returns:
- nothing
- Throws:
java.sql.SQLException- always
-
close
public void close() throws java.sql.SQLExceptionDoes the specialized work required to free this object's resources and that of it's parent class.- Specified by:
closein interfacejava.lang.AutoCloseable- Specified by:
closein interfacejava.sql.Statement- Overrides:
closein 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:
toStringin classjava.lang.Object- Returns:
- a String representation of this object
-
setPoolable
public void setPoolable(boolean poolable) throws java.sql.SQLException- Specified by:
setPoolablein interfacejava.sql.Statement- Overrides:
setPoolablein classjdbcStatement- Throws:
java.sql.SQLException
-
isPoolable
public boolean isPoolable() throws java.sql.SQLException- Specified by:
isPoolablein interfacejava.sql.Statement- Overrides:
isPoolablein classjdbcStatement- Throws:
java.sql.SQLException
-
unwrap
public <T> T unwrap(java.lang.Class<T> iface) throws java.sql.SQLException- Specified by:
unwrapin interfacejava.sql.Wrapper- Overrides:
unwrapin classjdbcStatement- Throws:
java.sql.SQLException
-
isWrapperFor
public boolean isWrapperFor(java.lang.Class<?> iface) throws java.sql.SQLException- Specified by:
isWrapperForin interfacejava.sql.Wrapper- Overrides:
isWrapperForin classjdbcStatement- Throws:
java.sql.SQLException
-
setRowId
public void setRowId(int parameterIndex, java.sql.RowId x) throws java.sql.SQLException- Specified by:
setRowIdin interfacejava.sql.PreparedStatement- Throws:
java.sql.SQLException
-
setNString
public void setNString(int parameterIndex, java.lang.String value) throws java.sql.SQLException- Specified by:
setNStringin 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:
setNCharacterStreamin interfacejava.sql.PreparedStatement- Throws:
java.sql.SQLException
-
setNClob
public void setNClob(int parameterIndex, java.sql.NClob value) throws java.sql.SQLException- Specified by:
setNClobin 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:
setClobin 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:
setBlobin 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:
setNClobin interfacejava.sql.PreparedStatement- Throws:
java.sql.SQLException
-
setSQLXML
public void setSQLXML(int parameterIndex, java.sql.SQLXML xmlObject) throws java.sql.SQLException- Specified by:
setSQLXMLin 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:
setAsciiStreamin 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:
setBinaryStreamin 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:
setCharacterStreamin interfacejava.sql.PreparedStatement- Throws:
java.sql.SQLException
-
setAsciiStream
public void setAsciiStream(int parameterIndex, java.io.InputStream x) throws java.sql.SQLException- Specified by:
setAsciiStreamin interfacejava.sql.PreparedStatement- Throws:
java.sql.SQLException
-
setBinaryStream
public void setBinaryStream(int parameterIndex, java.io.InputStream x) throws java.sql.SQLException- Specified by:
setBinaryStreamin interfacejava.sql.PreparedStatement- Throws:
java.sql.SQLException
-
setCharacterStream
public void setCharacterStream(int parameterIndex, java.io.Reader reader) throws java.sql.SQLException- Specified by:
setCharacterStreamin interfacejava.sql.PreparedStatement- Throws:
java.sql.SQLException
-
setNCharacterStream
public void setNCharacterStream(int parameterIndex, java.io.Reader value) throws java.sql.SQLException- Specified by:
setNCharacterStreamin interfacejava.sql.PreparedStatement- Throws:
java.sql.SQLException
-
setClob
public void setClob(int parameterIndex, java.io.Reader reader) throws java.sql.SQLException- Specified by:
setClobin interfacejava.sql.PreparedStatement- Throws:
java.sql.SQLException
-
setBlob
public void setBlob(int parameterIndex, java.io.InputStream inputStream) throws java.sql.SQLException- Specified by:
setBlobin interfacejava.sql.PreparedStatement- Throws:
java.sql.SQLException
-
setNClob
public void setNClob(int parameterIndex, java.io.Reader reader) throws java.sql.SQLException- Specified by:
setNClobin interfacejava.sql.PreparedStatement- Throws:
java.sql.SQLException
-
-