While scanning a Derby-style table function, Derby calls a preferred getXXX() method for each column, based on the column's data type. If Derby is running on a small device platform and presenting the JSR 169 interface to clients, then the methods which Derby calls are slightly different. This is because JSR 169 does not support BigDecimal.
The following table lists the preferred getXXX() method for each Derby data type.
| Column Type Declared by CREATE FUNCTION | getXXX() Method Called by Derby for JDBC 3.0 and 4.0 | getXXX() Method Called by Derby for JSR 169 |
|---|---|---|
| BIGINT | getLong() | Same |
| BLOB | getBlob() | Same |
| CHAR | getString() | Same |
| CHAR FOR BIT DATA | getBytes() | Same |
| CLOB | getClob() | Same |
| DATE | getDate() | Same |
| DECIMAL | getBigDecimal() | getString() |
| DOUBLE | getDouble() | Same |
| DOUBLE PRECISION | getDouble() | Same |
| FLOAT | getDouble() | Same |
| INTEGER | getInt() | Same |
| LONG VARCHAR | getString() | Same |
| LONG VARCHAR FOR BIT DATA | getBytes() | Same |
| NUMERIC | getBigDecimal() | getString() |
| REAL | getFloat() | Same |
| SMALLINT | getShort() | Same |
| TIME | getTime() | Same |
| TIMESTAMP | getTimestamp() | Same |
| VARCHAR | getString() | Same |
| VARCHAR FOR BIT DATA | getBytes() | Same |
| XML | Not supported | Not supported |