JDBC allows an IN parameter to be set to a Java input stream for
passing in large amounts of data in smaller chunks. When the statement is
run, the JDBC driver makes repeated calls to this input stream.
supports
the following JDBC stream methods for PreparedStatement objects:
- setBinaryStream
Use for streams that contain uninterpreted bytes
- setAsciiStream
Use for streams that contain ASCII characters
- setCharacterStream
Use for streams that contain characters
does not support
the setNCharacterStream method or the deprecated setUnicodeStream
method.
JDBC 3.0 requires that you specify the length of the
stream, and enforces
this requirement if your application runs on JDK 5 or earlier. If your application
runs on JDK 6, exposes
a JDBC 4.0 implementation, which lets you use the streaming interfaces without
having to specify the stream length. The stream object passed to
setBinaryStream and setAsciiStream can be either a standard Java
stream object or the user's own subclass that implements the standard
java.io.InputStream interface. The object passed to
setCharacterStream must be a subclass of the abstract
java.io.Reader class.
According
to the JDBC standard, streams can be stored only in columns with the data
types shown in the following table.
Streamable
JDBC Data Types
Column Data Type
Corresponding Java Type
AsciiStream
CharacterStream
BinaryStream
CLOB
java.sql.Clob
x
x
CHAR
x
x
VARCHAR
x
x
LONGVARCHAR
X
X
BINARY
x
x
x
BLOB
java.sql.Blob
x
x
x
VARBINARY
x
x
x
LONGVARBINARY
x
x
X
- A large X indicates the preferred target data type for the type of stream.
See .
- For applications using the client driver, if the stream is stored in a column of a type other than LONG VARCHAR
or LONG VARCHAR FOR BIT DATA, the entire stream must be able to fit into memory
at one time. Streams stored in LONG VARCHAR and LONG VARCHAR FOR BIT DATA
columns do not have this limitation.
- Streams cannot be stored in columns of the other built-in data types or
columns of user-defined data types.