org.hsqldb.jdbc

Class jdbcCallableStatement

Implemented Interfaces:
CallableStatement, PreparedStatement, Statement

public class jdbcCallableStatement
extends jdbcPreparedStatement
implements CallableStatement

<!-- start generic documentation --> The interface used to execute SQL stored procedures. The JDBC API provides a stored procedure SQL escape syntax that allows stored procedures to be called in a standard way for all RDBMSs. This escape syntax has one form that includes a result parameter and one that does not. If used, the result parameter must be registered as an OUT parameter. The other parameters can be used for input, output or both. Parameters are referred to sequentially, by number, with the first parameter being 1.
   {?= call <procedure-name>[<arg1>,<arg2>, ...]}
   {call <procedure-name>[<arg1>,<arg2>, ...]}
 

IN parameter values are set using the set methods inherited from PreparedStatement. The type of all OUT parameters must be registered prior to executing the stored procedure; their values are retrieved after execution via the get methods provided here.

A CallableStatement can return one ResultSet object or multiple ResultSet objects. Multiple ResultSet objects are handled using operations inherited from Statement.

For maximum portability, a call's ResultSet objects and update counts should be processed prior to getting the values of output parameters.

<!-- end generic documentation --> <!-- start Release-specific documentation -->

HSQLDB-Specific Information:

Since 1.7.2, the JDBC CallableStatement interface implementation has been broken out of the jdbcPreparedStatement class into this one.

With 1.7.2, some of the previously unsupported features of this interface are now supported, such as the parameterName-based setter methods.

More importantly, jdbcCallableStatement objects are now backed by a true compiled parameteric representation. Hence, there are now significant performance gains to be had by using a CallableStatement object instead of a Statement object, if a short-running CALL statement is to be executed more than a small number of times. Moreover, the recent work lays the foundation for work in a subsequenct release to support CallableStatement OUT and IN OUT style parameters, as well as the generation and retrieval of multiple results in response to the execution of a CallableStatement object.

For a more in-depth discussion of performance issues regarding 1.7.2 prepared and callable statement objects, please see overview section of jdbcPreparedStatment.


As with many DBMS, HSQLDB support for stored procedures is not provided in a completely standard fashion.

Beyond the XOpen/ODBC extended scalar functions, stored procedures are typically supported in ways that vary greatly from one DBMS implementation to the next. So, it is almost guaranteed that the code for a stored procedure written under a specific DBMS product will not work without at least some modification in the context of another vendor's product or even across a single vendor's product lines. Moving stored procedures from one DBMS product line to another almost invariably involves complex porting issues and often may not be possible at all. Be warned.

At present, HSQLDB stored procedures map directly onto the methods of compiled Java classes found on the classpath of the engine at runtime. This is done in a non-standard but fairly efficient way by issuing a class grant (and possibly method aliases) of the form:

 GRANT ALL ON CLASS "package.class" TO [<user-name> | PUBLIC]
 CREATE ALIAS <call-alias> FOR "package.class.method" -- optional
 
This has the effect of allowing the specified user(s) to access the set of uniquely named public static methods of the specified class, in either the role of SQL functions or stored procedures. For example:

 CONNECT <admin-user> PASSWORD <admin-user-password>;
 GRANT ALL ON CLASS "org.myorg.MyClass" TO PUBLIC;
 CREATE ALIAS sp_my_method FOR "org.myorg.MyClass.myMethod"
 CONNECT <any-user> PASSWORD <any-user-password>;
 SELECT "org.myorg.MyClass.myMethod"(column_1) FROM table_1;
 SELECT sp_my_method(column_1) FROM table_1;
 CALL 2 + "org.myorg.MyClass.myMethod"(-5);
 CALL 2 + sp_my_method(-5);
 
Please note the use of the term "uniquely named" above. Including 1.7.2, no support is provided to deterministically resolve overloaded method names, and there can be issues with inherited methods as well; currently, it is strongly recommended that developers creating stored procedure library classes for HSQLDB simply avoid designs such that SQL stored procedure calls attempt to resolve to:

  1. inherited public static methods
  2. overloaded public static methods
Also, please note that OUT and IN OUT parameters are not yet supported due to some unresolved low level support issues.

Including 1.7.2, the HSQLDB stored procedure call mechanism is essentially a thin wrap of the HSQLDB SQL function call mechanism, extended to include the more general HSQLDB SQL expression evaluation mechanism. In addition to stored procedure calls that resolve directly to Java method invocations, the extention provides the ability to evaluate simple SQL expressions, possibly containing Java method invocations, outside any INSERT, UPDATE, DELETE or SELECT statement context.

With HSQLDB, executing a CALL statement that produces an opaque (OTHER) or known scalar object reference has virtually the same effect as:

 CREATE TABLE DUAL (dummy VARCHAR);
 INSERT INTO DUAL VALUES(NULL);
 SELECT <simple-expression> FROM DUAL;
 
As a transitional measure, HSQLDB provides the ability to materialize a general result set in response to stored procedure execution. In this case, the stored procedure's Java method descriptor must specify a return type of java.lang.Object for external use (although at any point in the devlopment cycle, other, proprietary return types may accepted internally for engine development purposes). When HSQLDB detects that the runtime class of the resulting Object is elligible, an automatic internal unwrapping is performed to correctly expose the underlying result set to the client, whether local or remote.

Additionally, HSQLDB automatically detects if java.sql.Connection is the class of the first argument of any underlying Java method(s). If so, then the engine transparently supplies the internal Connection object corresponding to the Session executing the call, adjusting the positions of other arguments to suite the SQL context.

The features above are not intended to be permanent. Rather, the intention is to offer more general and powerful mechanisms in a future release; it is recommend to use them only as a temporary convenience.

For instance, one might be well advised to future-proof by writing HSQLDB-specific adapter methods that in turn call the real logic of an underlying generalized JDBC stored procedure library.

Here is a very simple example of an HSQLDB stored procedure generating a user-defined result set:

 package mypackage;

 class MyClass {

      public static Object mySp(Connection conn) throws SQLException {
          return conn.createStatement().executeQuery("select * from my_table");
      }
 }
 
Here is a refinement demonstrating no more than the bare essence of the idea behind a more portable style:
 package mypackage;

 import java.sql.ResultSet;
 import java.sql.SQLException;

 class MyLibraryClass {

      public static ResultSet mySp() throws SQLException {
          return ctx.getConnection().createStatement().executeQuery("select * from my_table");
      }
 }

 //--

 package myadaptorpackage;

 import java.sql.Connection;
 import java.sql.SQLException;

 class MyAdaptorClass {

      public static Object mySp(Connection conn) throws SQLException {
          MyLibraryClass.getCtx().setConnection(conn);
          return MyLibraryClass.mySp();
      }
 }
 
In a future release, it is intended to provided some new features that will support writing fairly portable JDBC-based stored procedure code:

(boucherb@users)
<!-- end Release-specific documentation -->
Author:
boucherb@users
Since:
1.7.2
See Also:
jdbcConnection.prepareCall, jdbcResultSet

Constructor Summary

jdbcCallableStatement(jdbcConnection c, String sql, int type)
Constructs a new jdbcCallableStatement with the specified connection and result type.

Method Summary

void
close()
Does the specialized work required to free this object's resources and that of it's parent classes.
Array
getArray(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC ARRAY parameter as an Array object in the Java programming language.
Array
getArray(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC ARRAY parameter as an java.sql.Array object in the Java programming language.
BigDecimal
getBigDecimal(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC NUMERIC parameter as a java.math.BigDecimal object with as many digits to the right of the decimal point as the value contains.
BigDecimal
getBigDecimal(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC NUMERIC parameter as a java.math.BigDecimal object with as many digits to the right of the decimal point as the value contains.
BigDecimal
getBigDecimal(int parameterIndex, int scale)
Deprecated. use getBigDecimal(int parameterIndex) or getBigDecimal(String parameterName)
Blob
getBlob(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC BLOB parameter as a java.sql.Blob object in the Java programming language.
Blob
getBlob(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC BLOB parameter as a java.sql.Blob object in the Java programming language.
boolean
getBoolean(String parameterName)
<!-- start generic documentation --> (JDBC4 modified:) Retrieves the value of a JDBC BIT or BOOLEAN parameter as a boolean in the Java programming language.
boolean
getBoolean(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC BIT parameter as a boolean in the Java programming language.
byte
getByte(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC TINYINT parameter as a byte in the Java programming language.
byte
getByte(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC TINYINT parameter as a byte in the Java programming language.
byte[]
getBytes(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC BINARY or VARBINARY parameter as an array of byte values in the Java programming language.
byte[]
getBytes(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC BINARY or VARBINARY parameter as an array of byte values in the Java programming language.
Clob
getClob(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC CLOB parameter as a java.sql.Clob object in the Java programming language.
Clob
getClob(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC CLOB parameter as a java.sql.Clob object in the Java programming language.
Date
getDate(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC DATE parameter as a java.sql.Date object.
Date
getDate(String parameterName, Calendar cal)
<!-- start generic documentation --> Retrieves the value of a JDBC DATE parameter as a java.sql.Date object, using the given Calendar object to construct the date.
Date
getDate(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC DATE parameter as a java.sql.Date object.
Date
getDate(int parameterIndex, Calendar cal)
<!-- start generic documentation --> Retrieves the value of the designated JDBC DATE parameter as a java.sql.Date object, using the given Calendar object to construct the date.
double
getDouble(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC DOUBLE parameter as a double in the Java programming language.
double
getDouble(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC DOUBLE parameter as a double in the Java programming language.
float
getFloat(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC FLOAT parameter as a float in the Java programming language.
float
getFloat(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC FLOAT parameter as a float in the Java programming language.
int
getInt(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC INTEGER parameter as an int in the Java programming language.
int
getInt(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC INTEGER parameter as an int in the Java programming language.
long
getLong(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC BIGINT parameter as a long in the Java programming language.
long
getLong(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC BIGINT parameter as a long in the Java programming language.
Object
getObject(String parameterName)
<!-- start generic documentation --> Retrieves the value of a parameter as an Object in the Java programming language.
Object
getObject(String parameterName, Map map)
<!-- start generic documentation --> Returns an object representing the value of OUT parameter parameterName and uses map for the custom mapping of the parameter value.
Object
getObject(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated parameter as an Object in the Java programming language.
Object
getObject(int parameterIndex, Map map)
<!-- start generic documentation --> Returns an object representing the value of OUT parameter parameterIndex and uses map for the custom mapping of the parameter value.
Ref
getRef(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC REF(<structured-type>) parameter as a Ref object in the Java programming language.
Ref
getRef(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC REF(<structured-type>) parameter as a java.sql.Ref object in the Java programming language.
short
getShort(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC SMALLINT parameter as a short in the Java programming language.
short
getShort(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC SMALLINT parameter as a short in the Java programming language.
String
getString(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC CHAR, VARCHAR, or LONGVARCHAR parameter as a String in the Java programming language.
String
getString(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC CHAR, VARCHAR, or LONGVARCHAR parameter as a String in the Java programming language.
Time
getTime(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC TIME parameter as a java.sql.Time object.
Time
getTime(String parameterName, Calendar cal)
<!-- start generic documentation --> Retrieves the value of a JDBC TIME parameter as a java.sql.Time object, using the given Calendar object to construct the time.
Time
getTime(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC TIME parameter as a java.sql.Time object.
Time
getTime(int parameterIndex, Calendar cal)
<!-- start generic documentation --> Retrieves the value of the designated JDBC TIME parameter as a java.sql.Time object, using the given Calendar object to construct the time.
Timestamp
getTimestamp(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC TIMESTAMP parameter as a java.sql.Timestamp object.
Timestamp
getTimestamp(String parameterName, Calendar cal)
<!-- start generic documentation --> Retrieves the value of a JDBC TIMESTAMP parameter as a java.sql.Timestamp object, using the given Calendar object to construct the Timestamp object.
Timestamp
getTimestamp(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC TIMESTAMP parameter as a java.sql.Timestamp object.
Timestamp
getTimestamp(int parameterIndex, Calendar cal)
<!-- start generic documentation --> Retrieves the value of the designated JDBC TIMESTAMP parameter as a java.sql.Timestamp object, using the given Calendar object to construct the Timestamp object.
java.net.URL
getURL(String parameterName)
<!-- start generic documentation --> Retrieves the value of a JDBC DATALINK parameter as a java.net.URL object.
java.net.URL
getURL(int parameterIndex)
<!-- start generic documentation --> Retrieves the value of the designated JDBC DATALINK parameter as a java.net.URL object.
void
registerOutParameter(String parameterName, int sqlType)
<!-- start generic documentation --> Registers the OUT parameter named parameterName to the JDBC type sqlType.
void
registerOutParameter(String parameterName, int sqlType, String typeName)
<!-- start generic documentation --> Registers the designated output parameter.
void
registerOutParameter(String parameterName, int sqlType, int scale)
<!-- start generic documentation --> Registers the parameter named parameterName to be of JDBC type sqlType.
void
registerOutParameter(int parameterIndex, int sqlType)
<!-- start generic documentation --> Registers the OUT parameter in ordinal position parameterIndex to the JDBC type sqlType.
void
registerOutParameter(int parameterIndex, int sqlType, String typeName)
<!-- start generic documentation --> Registers the designated output parameter.
void
registerOutParameter(int parameterIndex, int sqlType, int scale)
<!-- start generic documentation --> Registers the parameter in ordinal position parameterIndex to be of JDBC type sqlType.
void
setAsciiStream(String parameterName, java.io.InputStream x, int length)
<!-- start generic documentation --> Sets the designated parameter to the given input stream, which will have the specified number of bytes.
void
setBigDecimal(String parameterName, BigDecimal x)
<!-- start generic documentation --> Sets the designated parameter to the given java.math.BigDecimal value.
void
setBinaryStream(String parameterName, java.io.InputStream x, int length)
<!-- start generic documentation --> Sets the designated parameter to the given input stream, which will have the specified number of bytes.
void
setBoolean(String parameterName, boolean x)
<!-- start generic documentation --> Sets the designated parameter to the given Java boolean value.
void
setByte(String parameterName, byte x)
<!-- start generic documentation --> Sets the designated parameter to the given Java byte value.
void
setBytes(String parameterName, byte[] x)
<!-- start generic documentation --> Sets the designated parameter to the given Java array of bytes.
void
setCharacterStream(String parameterName, java.io.Reader reader, int length)
<!-- start generic documentation --> Sets the designated parameter to the given Reader object, which is the given number of characters long.
void
setDate(String parameterName, Date x)
<!-- start generic documentation --> (JDBC4 clarification:) Sets the designated parameter to the given java.sql.Date value using the default time zone of the virtual machine that is running the application.
void
setDate(String parameterName, Date x, Calendar cal)
<!-- start generic documentation --> Sets the designated parameter to the given java.sql.Date value, using the given Calendar object.
void
setDouble(String parameterName, double x)
<!-- start generic documentation --> Sets the designated parameter to the given Java double value.
void
setFloat(String parameterName, float x)
<!-- start generic documentation --> Sets the designated parameter to the given Java float value.
void
setInt(String parameterName, int x)
<!-- start generic documentation --> Sets the designated parameter to the given Java int value.
void
setLong(String parameterName, long x)
<!-- start generic documentation --> Sets the designated parameter to the given Java long value.
void
setNull(String parameterName, int sqlType)
<!-- start generic documentation --> Sets the designated parameter to SQL NULL.
void
setNull(String parameterName, int sqlType, String typeName)
<!-- start generic documentation --> Sets the designated parameter to SQL NULL.
void
setObject(String parameterName, Object x)
<!-- start generic documentation --> Sets the value of the designated parameter with the given object.
void
setObject(String parameterName, Object x, int targetSqlType)
<!-- start generic documentation --> Sets the value of the designated parameter with the given object.
void
setObject(String parameterName, Object x, int targetSqlType, int scale)
<!-- start generic documentation --> Sets the value of the designated parameter with the given object.
void
setShort(String parameterName, short x)
<!-- start generic documentation --> Sets the designated parameter to the given Java short value.
void
setString(String parameterName, String x)
<!-- start generic documentation --> Sets the designated parameter to the given Java String value.
void
setTime(String parameterName, Time x)
<!-- start generic documentation --> Sets the designated parameter to the given java.sql.Time value.
void
setTime(String parameterName, Time x, Calendar cal)
<!-- start generic documentation --> Sets the designated parameter to the given java.sql.Time value, using the given Calendar object.
void
setTimestamp(String parameterName, Timestamp x)
<!-- start generic documentation --> Sets the designated parameter to the given java.sql.Timestamp value.
void
setTimestamp(String parameterName, Timestamp x, Calendar cal)
<!-- start generic documentation --> Sets the designated parameter to the given java.sql.Timestamp value, using the given Calendar object.
void
setURL(String parameterName, java.net.URL val)
<!-- start generic documentation --> Sets the designated parameter to the given java.net.URL object.
boolean
wasNull()
<!-- start generic documentation --> Retrieves whether the last OUT parameter read had the value of SQL NULL.

Methods inherited from class org.hsqldb.jdbc.jdbcPreparedStatement

addBatch, addBatch, clearParameters, close, execute, execute, executeBatch, executeQuery, executeQuery, executeUpdate, executeUpdate, getMetaData, getParameterMetaData, setArray, setAsciiStream, setBigDecimal, setBinaryStream, setBlob, setBoolean, setByte, setBytes, setCharacterStream, setClob, setDate, setDate, setDouble, setEscapeProcessing, setFloat, setInt, setLong, setNull, setNull, setObject, setObject, setObject, setRef, setShort, setString, setTime, setTime, setTimestamp, setTimestamp, setURL, setUnicodeStream, toString

Methods inherited from class org.hsqldb.jdbc.jdbcStatement

addBatch, cancel, clearBatch, clearWarnings, close, execute, execute, execute, execute, executeBatch, executeQuery, executeUpdate, executeUpdate, executeUpdate, executeUpdate, getConnection, getFetchDirection, getFetchSize, getGeneratedKeys, getMaxFieldSize, getMaxRows, getMoreResults, getMoreResults, getQueryTimeout, getResultSet, getResultSetConcurrency, getResultSetHoldability, getResultSetType, getUpdateCount, getWarnings, setCursorName, setEscapeProcessing, setFetchDirection, setFetchSize, setMaxFieldSize, setMaxRows, setQueryTimeout

Constructor Details

jdbcCallableStatement

public jdbcCallableStatement(jdbcConnection c,
                             String sql,
                             int type)
            throws org.hsqldb.HsqlException,
                   SQLException
Constructs a new jdbcCallableStatement with the specified connection and result type.
Parameters:
c - the connection on which this statement will execute
sql - the SQL statement this object represents
type - the type of result this statement will produce
Throws:
org.hsqldb.HsqlException - if the statement is not accepted by the database

Method Details

close

public void close()
            throws SQLException
Does the specialized work required to free this object's resources and that of it's parent classes.

Overrides:
close in interface jdbcPreparedStatement

getArray

public Array getArray(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC ARRAY parameter as an Array object in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value as an Array object in Java programming language. If the value was SQL NULL, the value null is returned.
Since:
JDK 1.4, HSQLDB 1.7.0

getArray

public Array getArray(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC ARRAY parameter as an java.sql.Array object in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value as an Array object in the Java programming language. If the value was SQL NULL, the value null is returned.
Since:
JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)

getBigDecimal

public BigDecimal getBigDecimal(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC NUMERIC parameter as a java.math.BigDecimal object with as many digits to the right of the decimal point as the value contains.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value in full precision. If the value is SQL NULL, the result is null.
Since:
JDK 1.4, HSQLDB 1.7.0

getBigDecimal

public BigDecimal getBigDecimal(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC NUMERIC parameter as a java.math.BigDecimal object with as many digits to the right of the decimal point as the value contains.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value in full precision. If the value is SQL NULL, the result is null.
Since:
JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)

getBigDecimal

public BigDecimal getBigDecimal(int parameterIndex,
                                int scale)
            throws SQLException

Deprecated. use getBigDecimal(int parameterIndex) or getBigDecimal(String parameterName)

<!-- start generic documentation --> Retrieves the value of the designated JDBC NUMERIC parameter as a java.math.BigDecimal object with scale digits to the right of the decimal point.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
scale - the number of digits to the right of the decimal point
Returns:
the parameter value. If the value is SQL NULL, the result is null.

getBlob

public Blob getBlob(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC BLOB parameter as a java.sql.Blob object in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value as a Blob object in the Java programming language. If the value was SQL NULL, the value null is returned.
Since:
JDK 1.4, HSQLDB 1.7.0

getBlob

public Blob getBlob(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC BLOB parameter as a java.sql.Blob object in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value as a Blob object in the Java programming language. If the value was SQL NULL, the value null is returned.
Since:
JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)

getBoolean

public boolean getBoolean(String parameterName)
            throws SQLException
<!-- start generic documentation --> (JDBC4 modified:) Retrieves the value of a JDBC BIT or BOOLEAN parameter as a boolean in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value. If the value is SQL NULL, the result is false.
Since:
JDK 1.4, HSQLDB 1.7.0

getBoolean

public boolean getBoolean(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC BIT parameter as a boolean in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value. If the value is SQL NULL, the result is false.

getByte

public byte getByte(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC TINYINT parameter as a byte in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value. If the value is SQL NULL, the result is 0.
Since:
JDK 1.4, HSQLDB 1.7.0

getByte

public byte getByte(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC TINYINT parameter as a byte in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value. If the value is SQL NULL, the result is 0.

getBytes

public byte[] getBytes(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC BINARY or VARBINARY parameter as an array of byte values in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value. If the value is SQL NULL, the result is null.
Since:
JDK 1.4, HSQLDB 1.7.0

getBytes

public byte[] getBytes(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC BINARY or VARBINARY parameter as an array of byte values in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value. If the value is SQL NULL, the result is null.

getClob

public Clob getClob(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC CLOB parameter as a java.sql.Clob object in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value as a Clob object in the Java programming language. If the value was SQL NULL, the value null is returned.
Since:
JDK 1.4, HSQLDB 1.7.0

getClob

public Clob getClob(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC CLOB parameter as a java.sql.Clob object in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value as a Clob object in the Java programming language. If the value was SQL NULL, the value null is returned.
Since:
JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)

getDate

public Date getDate(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC DATE parameter as a java.sql.Date object.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value. If the value is SQL NULL, the result is null.
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
setDate

getDate

public Date getDate(String parameterName,
                    Calendar cal)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC DATE parameter as a java.sql.Date object, using the given Calendar object to construct the date. With a Calendar object, the driver can calculate the date taking into account a custom timezone and locale. If no Calendar object is specified, the d river uses the default timezone and locale.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
cal - the Calendar object the driver will use to construct the date
Returns:
the parameter value. If the value is SQL NULL, the result is null.
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
setDate

getDate

public Date getDate(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC DATE parameter as a java.sql.Date object.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value. If the value is SQL NULL, the result is null.
See Also:
setDate

getDate

public Date getDate(int parameterIndex,
                    Calendar cal)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC DATE parameter as a java.sql.Date object, using the given Calendar object to construct the date. With a Calendar object, the driver can calculate the date taking into account a custom timezone and locale. If no Calendar object is specified, the driver uses the default timezone and locale.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
cal - the Calendar object the driver will use to construct the date
Returns:
the parameter value. If the value is SQL NULL, the result is null.
Since:
JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
See Also:
setDate

getDouble

public double getDouble(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC DOUBLE parameter as a double in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value. If the value is SQL NULL, the result is 0.
Since:
JDK 1.4, HSQLDB 1.7.0

getDouble

public double getDouble(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC DOUBLE parameter as a double in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value. If the value is SQL NULL, the result is 0.

getFloat

public float getFloat(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC FLOAT parameter as a float in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value. If the value is SQL NULL, the result is 0.
Since:
JDK 1.4, HSQLDB 1.7.0

getFloat

public float getFloat(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC FLOAT parameter as a float in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value. If the value is SQL NULL, the result is 0.

getInt

public int getInt(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC INTEGER parameter as an int in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value. If the value is SQL NULL, the result is 0.
Since:
JDK 1.4, HSQLDB 1.7.0

getInt

public int getInt(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC INTEGER parameter as an int in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value. If the value is SQL NULL, the result is 0.

getLong

public long getLong(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC BIGINT parameter as a long in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value. If the value is SQL NULL, the result is 0.
Since:
JDK 1.4, HSQLDB 1.7.0

getLong

public long getLong(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC BIGINT parameter as a long in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value. If the value is SQL NULL, the result is 0.

getObject

public Object getObject(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a parameter as an Object in the Java programming language. If the value is an SQL NULL, the driver returns a Java null.

This method returns a Java object whose type corresponds to the JDBC type that was registered for this parameter using the method registerOutParameter. By registering the target JDBC type as java.sql.Types.OTHER, this method can be used to read database-specific abstract data types.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
A java.lang.Object holding the OUT parameter value.
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
java.sql.Types, setObject

getObject

public Object getObject(String parameterName,
                        Map map)
            throws SQLException
<!-- start generic documentation --> Returns an object representing the value of OUT parameter parameterName and uses map for the custom mapping of the parameter value.

This method returns a Java object whose type corresponds to the JDBC type that was registered for this parameter using the method registerOutParameter. By registering the target JDBC type as java.sql.Types.OTHER, this method can be used to read database-specific abstract data types.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
map - the mapping from SQL type names to Java classes
Returns:
a java.lang.Object holding the OUT parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
setObject

getObject

public Object getObject(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated parameter as an Object in the Java programming language. If the value is an SQL NULL, the driver returns a Java null.

This method returns a Java object whose type corresponds to the JDBC type that was registered for this parameter using the method registerOutParameter. By registering the target JDBC type as java.sql.Types.OTHER, this method can be used to read database-specific abstract data types.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
A java.lang.Object holding the OUT parameter value
See Also:
java.sql.Types, setObject

getObject

public Object getObject(int parameterIndex,
                        Map map)
            throws SQLException
<!-- start generic documentation --> Returns an object representing the value of OUT parameter parameterIndex and uses map for the custom mapping of the parameter value.

This method returns a Java object whose type corresponds to the JDBC type that was registered for this parameter using the method registerOutParameter. By registering the target JDBC type as java.sql.Types.OTHER, this method can be used to read database-specific abstract data types.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
map - the mapping from SQL type names to Java classes
Returns:
a java.lang.Object holding the OUT parameter value
Since:
JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
See Also:
setObject

getRef

public Ref getRef(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC REF(<structured-type>) parameter as a Ref object in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value as a Ref object in the Java programming language. If the value was SQL NULL, the value null is returned.
Since:
JDK 1.4, HSQLDB 1.7.0

getRef

public Ref getRef(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC REF(<structured-type>) parameter as a java.sql.Ref object in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value as a Ref object in the Java programming language. If the value was SQL NULL, the value null is returned.
Since:
JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)

getShort

public short getShort(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC SMALLINT parameter as a short in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value. If the value is SQL NULL, the result is 0.
Since:
JDK 1.4, HSQLDB 1.7.0

getShort

public short getShort(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC SMALLINT parameter as a short in the Java programming language.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value. If the value is SQL NULL, the result is 0.

getString

public String getString(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC CHAR, VARCHAR, or LONGVARCHAR parameter as a String in the Java programming language.

For the fixed-length type JDBC CHAR, the String object returned has exactly the same value the (JDBC4 clarification:) SQL CHAR value had in the database, including any padding added by the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value. If the value is SQL NULL, the result is null.
Since:
JDK 1.4, HSQLDB 1.7.0

getString

public String getString(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC CHAR, VARCHAR, or LONGVARCHAR parameter as a String in the Java programming language.

For the fixed-length type JDBC CHAR, the String object returned has exactly the same value the (JDBC4 clarification:) SQL CHAR value had in the database, including any padding added by the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value. If the value is SQL NULL, the result is null.

getTime

public Time getTime(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC TIME parameter as a java.sql.Time object.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value. If the value is SQL NULL, the result is null.
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
setTime

getTime

public Time getTime(String parameterName,
                    Calendar cal)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC TIME parameter as a java.sql.Time object, using the given Calendar object to construct the time. With a Calendar object, the driver can calculate the time taking into account a custom timezone and locale. If no Calendar object is specified, the driver uses the default timezone and locale.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
cal - the Calendar object the driver will use to construct the time
Returns:
the parameter value; if the value is SQL NULL, the result is null.
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
setTime

getTime

public Time getTime(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC TIME parameter as a java.sql.Time object.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value. If the value is SQL NULL, the result is null.
See Also:
setTime

getTime

public Time getTime(int parameterIndex,
                    Calendar cal)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC TIME parameter as a java.sql.Time object, using the given Calendar object to construct the time. With a Calendar object, the driver can calculate the time taking into account a custom timezone and locale. If no Calendar object is specified, the driver uses the default timezone and locale.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
cal - the Calendar object the driver will use to construct the time
Returns:
the parameter value; if the value is SQL NULL, the result is null.
Since:
JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
See Also:
setTime

getTimestamp

public Timestamp getTimestamp(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC TIMESTAMP parameter as a java.sql.Timestamp object.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value. If the value is SQL NULL, the result is null.
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
setTimestamp

getTimestamp

public Timestamp getTimestamp(String parameterName,
                              Calendar cal)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC TIMESTAMP parameter as a java.sql.Timestamp object, using the given Calendar object to construct the Timestamp object. With a Calendar object, the driver can calculate the timestamp taking into account a custom timezone and locale. If no Calendar object is specified, the driver uses the default timezone and locale.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
cal - the Calendar object the driver will use to construct the timestamp
Returns:
the parameter value. If the value is SQL NULL, the result is null.
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
setTimestamp

getTimestamp

public Timestamp getTimestamp(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC TIMESTAMP parameter as a java.sql.Timestamp object.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
Returns:
the parameter value. If the value is SQL NULL, the result is null.
See Also:
setTimestamp

getTimestamp

public Timestamp getTimestamp(int parameterIndex,
                              Calendar cal)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC TIMESTAMP parameter as a java.sql.Timestamp object, using the given Calendar object to construct the Timestamp object. With a Calendar object, the driver can calculate the timestamp taking into account a custom timezone and locale. If no Calendar object is specified, the driver uses the default timezone and locale.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
cal - the Calendar object the driver will use to construct the timestamp
Returns:
the parameter value. If the value is SQL NULL, the result is null.
Since:
JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
See Also:
setTimestamp

getURL

public java.net.URL getURL(String parameterName)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of a JDBC DATALINK parameter as a java.net.URL object.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
Returns:
the parameter value as a java.net.URL object in the Java programming language. If the value was SQL NULL, the value null is returned.
Since:
JDK 1.4, HSQLDB 1.7.0

getURL

public java.net.URL getURL(int parameterIndex)
            throws SQLException
<!-- start generic documentation --> Retrieves the value of the designated JDBC DATALINK parameter as a java.net.URL object.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2,...
Returns:
a java.net.URL object that represents the JDBC DATALINK value used as the designated parameter
Since:
JDK 1.4, HSQLDB 1.7.0

registerOutParameter

public void registerOutParameter(String parameterName,
                                 int sqlType)
            throws SQLException
<!-- start generic documentation --> Registers the OUT parameter named parameterName to the JDBC type sqlType. All OUT parameters must be registered before a stored procedure is executed.

The JDBC type specified by sqlType for an OUT parameter determines the Java type that must be used in the get method to read the value of that parameter.

If the JDBC type expected to be returned to this output parameter is specific to this particular database, sqlType should be java.sql.Types.OTHER. The method getObject retrieves the value.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
sqlType - the JDBC type code defined by java.sql.Types. If the parameter is of JDBC type NUMERIC or DECIMAL, the version of registerOutParameter that accepts a scale value should be used.
Since:
JDK 1.4, HSQL 1.7.0
See Also:
java.sql.Types

registerOutParameter

public void registerOutParameter(String parameterName,
                                 int sqlType,
                                 String typeName)
            throws SQLException
<!-- start generic documentation --> Registers the designated output parameter. This version of the method registerOutParameter should be used for a user-named or REF output parameter. Examples of user-named types include: STRUCT, DISTINCT, JAVA_OBJECT, and named array types.

(JDBC4 clarification:) All OUT parameters must be registered before a stored procedure is executed.

For a user-named parameter the fully-qualified SQL type name of the parameter should also be given, while a REF parameter requires that the fully-qualified type name of the referenced type be given. A JDBC driver that does not need the type code and type name information may ignore it. To be portable, however, applications should always provide these values for user-named and REF parameters. Although it is intended for user-named and REF parameters, this method may be used to register a parameter of any JDBC type. If the parameter does not have a user-named or REF type, the typeName parameter is ignored.

Note: When reading the value of an out parameter, you must use the getXXX method whose Java type XXX corresponds to the parameter's registered SQL type.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
sqlType - a value from java.sql.Types
typeName - the fully-qualified name of an SQL structured type
Since:
JDK 1.4, HSQL 1.7.0
See Also:
java.sql.Types

registerOutParameter

public void registerOutParameter(String parameterName,
                                 int sqlType,
                                 int scale)
            throws SQLException
<!-- start generic documentation --> Registers the parameter named parameterName to be of JDBC type sqlType. (JDBC4 clarification:) All OUT parameters must be registered before a stored procedure is executed.

The JDBC type specified by sqlType for an OUT parameter determines the Java type that must be used in the get method to read the value of that parameter.

This version of registerOutParameter should be used when the parameter is of JDBC type NUMERIC or DECIMAL.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
sqlType - SQL type code defined by java.sql.Types.
scale - the desired number of digits to the right of the decimal point. It must be greater than or equal to zero.
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
java.sql.Types

registerOutParameter

public void registerOutParameter(int parameterIndex,
                                 int sqlType)
            throws SQLException
<!-- start generic documentation --> Registers the OUT parameter in ordinal position parameterIndex to the JDBC type sqlType. All OUT parameters must be registered before a stored procedure is executed.

The JDBC type specified by sqlType for an OUT parameter determines the Java type that must be used in the get method to read the value of that parameter.

If the JDBC type expected to be returned to this output parameter is specific to this particular database, sqlType should be java.sql.Types.OTHER. The method getObject retrieves the value.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
sqlType - the JDBC type code defined by java.sql.Types. If the parameter is of JDBC type NUMERIC or DECIMAL, the version of registerOutParameter that accepts a scale value should be used.
See Also:
java.sql.Types

registerOutParameter

public void registerOutParameter(int parameterIndex,
                                 int sqlType,
                                 String typeName)
            throws SQLException
<!-- start generic documentation --> Registers the designated output parameter. This version of the method registerOutParameter should be used for a user-defined or REF output parameter. Examples of user-defined types include: STRUCT, DISTINCT, JAVA_OBJECT, and named array types.

(JDBC4 claraification:) All OUT parameters must be registered before a stored procedure is executed.

For a user-defined parameter, the fully-qualified SQL type name of the parameter should also be given, while a REF parameter requires that the fully-qualified type name of the referenced type be given. A JDBC driver that does not need the type code and type name information may ignore it. To be portable, however, applications should always provide these values for user-defined and REF parameters. Although it is intended for user-defined and REF parameters, this method may be used to register a parameter of any JDBC type. If the parameter does not have a user-defined or REF type, the typeName parameter is ignored.

Note: When reading the value of an out parameter, you must use the getter method whose Java type corresponds to the parameter's registered SQL type.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2,...
sqlType - a value from java.sql.Types
typeName - the fully-qualified name of an SQL structured type
Since:
JDK 1.2 (JDK 1.1.x developers: read the new overview for jdbcPreparedStatement)
See Also:
java.sql.Types

registerOutParameter

public void registerOutParameter(int parameterIndex,
                                 int sqlType,
                                 int scale)
            throws SQLException
<!-- start generic documentation --> Registers the parameter in ordinal position parameterIndex to be of JDBC type sqlType. This method must be called before a stored procedure is executed.

The JDBC type specified by sqlType for an OUT parameter determines the Java type that must be used in the get method to read the value of that parameter.

This version of registerOutParameter should be used when the parameter is of JDBC type NUMERIC or DECIMAL.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterIndex - the first parameter is 1, the second is 2, and so on
sqlType - the SQL type code defined by java.sql.Types.
scale - the desired number of digits to the right of the decimal point. It must be greater than or equal to zero.
See Also:
java.sql.Types

setAsciiStream

public void setAsciiStream(String parameterName,
                           java.io.InputStream x,
                           int length)
            throws SQLException
<!-- start generic documentation --> 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 a LONGVARCHAR parameter, it may be more practical to send it via a java.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.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the Java input stream that contains the ASCII parameter value
length - the number of bytes in the stream
Since:
JDK 1.4, HSQLDB 1.7.0

setBigDecimal

public void setBigDecimal(String parameterName,
                          BigDecimal x)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given java.math.BigDecimal value. The driver converts this to an SQL NUMERIC value when it sends it to the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getBigDecimal

setBinaryStream

public void setBinaryStream(String parameterName,
                            java.io.InputStream x,
                            int length)
            throws SQLException
<!-- start generic documentation --> 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 a LONGVARBINARY parameter, it may be more practical to send it via a java.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.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the java input stream which contains the binary parameter value
length - the number of bytes in the stream
Since:
JDK 1.4, HSQLDB 1.7.0

setBoolean

public void setBoolean(String parameterName,
                       boolean x)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given Java boolean value. (JDBC4 clarification:) The driver converts this to an SQL BIT or BOOLEAN value when it sends it to the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getBoolean

setByte

public void setByte(String parameterName,
                    byte x)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given Java byte value. The driver converts this to an SQL TINYINT value when it sends it to the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getByte

setBytes

public void setBytes(String parameterName,
                     byte[] x)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given Java array of bytes. The driver converts this to an SQL VARBINARY or LONGVARBINARY (depending on the argument's size relative to the driver's limits on VARBINARY values) when it sends it to the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getBytes

setCharacterStream

public void setCharacterStream(String parameterName,
                               java.io.Reader reader,
                               int length)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given Reader object, which is the given number of characters long. When a very large UNICODE value is input to a LONGVARCHAR parameter, it may be more practical to send it via a java.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.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
reader - the java.io.Reader object that contains the UNICODE data used as the designated parameter
length - the number of characters in the stream
Since:
JDK 1.4, HSQLDB 1.7.0

setDate

public void setDate(String parameterName,
                    Date x)
            throws SQLException
<!-- start generic documentation --> (JDBC4 clarification:) Sets the designated parameter to the given java.sql.Date value using the default time zone of the virtual machine that is running the application. The driver converts this to an SQL DATE value when it sends it to the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getDate

setDate

public void setDate(String parameterName,
                    Date x,
                    Calendar cal)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given java.sql.Date value, using the given Calendar object. The driver uses the Calendar object to construct an SQL DATE value, which the driver then sends to the database. With a a Calendar object, the driver can calculate the date taking into account a custom timezone. If no Calendar object is specified, the driver uses the default timezone, which is that of the virtual machine running the application.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
cal - the Calendar object the driver will use to construct the date
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getDate

setDouble

public void setDouble(String parameterName,
                      double x)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given Java double value. The driver converts this to an SQL DOUBLE value when it sends it to the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getDouble

setFloat

public void setFloat(String parameterName,
                     float x)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given Java float value. The driver converts this to an SQL FLOAT value when it sends it to the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getFloat

setInt

public void setInt(String parameterName,
                   int x)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given Java int value. The driver converts this to an SQL INTEGER value when it sends it to the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getInt

setLong

public void setLong(String parameterName,
                    long x)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given Java long value. The driver converts this to an SQL BIGINT value when it sends it to the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getLong

setNull

public void setNull(String parameterName,
                    int sqlType)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to SQL NULL.

Note: You must specify the parameter's SQL type.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
sqlType - the SQL type code defined in java.sql.Types
Since:
JDK 1.4, HSQLDB 1.7.0

setNull

public void setNull(String parameterName,
                    int sqlType,
                    String typeName)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to SQL NULL. This version of the method setNull 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.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
sqlType - a value from java.sql.Types
typeName - the fully-qualified name of an SQL user-defined type; ignored if the parameter is not a user-defined type or SQL REF value
Since:
JDK 1.4, HSQLDB 1.7.0

setObject

public void setObject(String parameterName,
                      Object x)
            throws SQLException
<!-- start generic documentation --> Sets the value of the designated parameter with the given object. The second parameter must be of type Object; therefore, the java.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 method SQLData.writeSQL to write it to the SQL data stream. If, on the other hand, the object is of a class implementing Ref, Blob, Clob, Struct, or Array, 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.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the object containing the input parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getObject

setObject

public void setObject(String parameterName,
                      Object x,
                      int targetSqlType)
            throws SQLException
<!-- start generic documentation --> Sets the value of the designated parameter with the given object. This method is like the method setObject above, except that it assumes a scale of zero.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the object containing the input parameter value
targetSqlType - the SQL type (as defined in java.sql.Types) to be sent to the database
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getObject

setObject

public void setObject(String parameterName,
                      Object x,
                      int targetSqlType,
                      int scale)
            throws SQLException
<!-- start generic documentation --> 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 method SQLData.writeSQL to write it to the SQL data stream. If, on the other hand, the object is of a class implementing Ref, Blob, Clob, Struct, or Array, 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 datatabase- specific abstract data types.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the object containing the input parameter value
targetSqlType - 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.
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
java.sql.Types, getObject

setShort

public void setShort(String parameterName,
                     short x)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given Java short value. The driver converts this to an SQL SMALLINT value when it sends it to the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getShort

setString

public void setString(String parameterName,
                      String x)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given Java String value. The driver converts this to an SQL VARCHAR or LONGVARCHAR value (depending on the argument's size relative to the driver's limits on VARCHAR values) when it sends it to the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getString

setTime

public void setTime(String parameterName,
                    Time x)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given java.sql.Time value. The driver converts this to an SQL TIME value when it sends it to the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getTime

setTime

public void setTime(String parameterName,
                    Time x,
                    Calendar cal)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given java.sql.Time value, using the given Calendar object. The driver uses the Calendar object to construct an SQL TIME value, which the driver then sends to the database. With a a Calendar object, the driver can calculate the time taking into account a custom timezone. If no Calendar object is specified, the driver uses the default timezone, which is that of the virtual machine running the application.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
cal - the Calendar object the driver will use to construct the time
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getTime

setTimestamp

public void setTimestamp(String parameterName,
                         Timestamp x)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given java.sql.Timestamp value. The driver converts this to an SQL TIMESTAMP value when it sends it to the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getTimestamp

setTimestamp

public void setTimestamp(String parameterName,
                         Timestamp x,
                         Calendar cal)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given java.sql.Timestamp value, using the given Calendar object. The driver uses the Calendar object to construct an SQL TIMESTAMP value, which the driver then sends to the database. With a Calendar object, the driver can calculate the timestamp taking into account a custom timezone. If no Calendar object is specified, the driver uses the default timezone, which is that of the virtual machine running the application.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

Starting with 1.7.2, HSLQDB supports this.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
x - the parameter value
cal - the Calendar object the driver will use to construct the timestamp
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getTimestamp

setURL

public void setURL(String parameterName,
                   java.net.URL val)
            throws SQLException
<!-- start generic documentation --> Sets the designated parameter to the given java.net.URL object. The driver converts this to an SQL DATALINK value when it sends it to the database.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Parameters:
parameterName - the name of the parameter
val - the parameter value
Since:
JDK 1.4, HSQLDB 1.7.0
See Also:
getURL

wasNull

public boolean wasNull()
            throws SQLException
<!-- start generic documentation --> Retrieves whether the last OUT parameter read had the value of SQL NULL. Note that this method should be called only after calling a getter method; otherwise, there is no value to use in determining whether it is null or not.

<!-- end generic documentation --> <!-- start release-specific documentation -->

HSQLDB-Specific Information:

HSQLDB 1.7.2 does not support this feature.

Calling this method always throws an SQLException.

<!-- end release-specific documentation -->
Returns:
true if the last parameter read was SQL NULL; false otherwise

Copyright B) 2001 - 2005 HSQL Development Group. All Rights Reserved.