In Derby, the java.sql.Types are mapped to SQL data types
The following table shows the mapping of
java.sql.Types to
SQL types.
Table 1. Mapping of java.sql.Types
to SQL Types
java.sql.Types |
SQL Types |
BIGINT |
BIGINT |
BINARY |
CHAR FOR BIT DATA |
BIT1 |
CHAR FOR BIT DATA |
BLOB |
BLOB (JDBC 2.0 and up) |
CHAR |
CHAR |
CLOB |
CLOB (JDBC 2.0 and up) |
DATE |
DATE |
DECIMAL |
DECIMAL |
DOUBLE |
DOUBLE PRECISION |
FLOAT |
DOUBLE PRECISION2 |
INTEGER |
INTEGER |
LONGVARBINARY |
LONG VARCHAR FOR BIT DATA |
LONGVARCHAR |
LONG VARCHAR |
NULL |
Not a data type; always a value of a particular type |
NUMERIC |
DECIMAL |
REAL |
REAL |
SMALLINT |
SMALLINT |
SQLXML3 |
XML |
TIME |
TIME |
TIMESTAMP |
TIMESTAMP |
VARBINARY |
VARCHAR FOR BIT DATA |
VARCHAR |
VARCHAR |
Notes:
- BIT is only valid in JDBC 2.0 and earlier environments.
- Values can be passed in using the FLOAT type code; however,
these are stored as DOUBLE PRECISION values, and so always have the type code
DOUBLE when retrieved.
- SQLXML is only valid in JDBC 4.0 and later environments. SQLXML
corresponds to the SQL type XML in Derby.
However, Derby does not
recognize the java.sql.Types.SQLXML data type and does not support any JDBC-side
operations for the XML data type. Support for XML and the related operators
is implemented only at the SQL layer. See XML
data types for more.