Data Type Support

This section covers data type considerations for JMS/XLA.

Data Type Mapping

There are MapMessage access methods for data types supported by TimesTen.

See Table 6-16. For more information about data types, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.

Table 6-16 Data Type Mapping

TimesTen column type	Read with MapMessage method...
`CHAR(n)`	`getString()`
`VARCHAR(n)`	`getString()`
`NCHAR(n)`	`getString()`
`NVARCHAR(n)`	`getString()`
`NVARCHAR2(n)`	`getString()`
`DOUBLE`	`getString()` Can be converted to `BigDecimal` or to `Double` by the application.
`FLOAT`	`getString()` Can be converted to `BigDecimal` or to `Double` by the application.
`DECIMAL(p,s)`	`getString()` Can be converted to `BigDecimal` or to `Double` by the application.
`NUMERIC(p,s)`	`getString()` Can be converted to `BigDecimal` or to `Double` by the application.
`INTEGER`	`getInt()`
`SMALLINT`	`getShort()`
`TINYINT`	`getShort()`
`BINARY(n)`	`getBytes()`
`VARBINARY(n)`	`getBytes()`
`DATE`	`getLong()`, `getString()` The `getLong()` method returns microseconds since epoch (00:00:00 UTC, January 1, 1970). Can be converted to `Date` or `Calendar` by the application.
`TIME`	`getString()` Can be converted to `Date` or `Calendar` by the application.
`TIMESTAMP`	`getLong()`, `getString()` The `getLong()` method returns microseconds since epoch (00:00:00 UTC, January 1, 1970). It truncates nanoseconds. Use `getString()` if you require nanosecond precision. Can be converted to `Date` or `Calendar` by the application.
`TT_CHAR`	`getString()`
`TT_VARCHAR`	`getString()`
`TT_NCHAR`	`getString()`
`TT_NVARCHAR`	`getString()`
`ORA_CHAR`	`getString()`
`ORA_VARCHAR`	`getString()`
`ORA_NCHAR`	`getString()`
`ORA_NVARCHAR2`	`getString()`
`VARCHAR2`	`getString()`
`TT_TINYINT`	`getShort()`
`TT_SMALLINT`	`getShort()`
`TT_INTEGER`	`getInt()`
`TT_BIGINT`	`getLong()`
`BINARY_FLOAT`	`getFloat()`
`BINARY_DOUBLE`	`getDouble()`
`REAL`	`getFloat()`
`NUMBER`	`getString()`
`ORA_NUMBER`	`getString()`
`TT_TIME`	`getString()`
`TT_DATE`	`getLong()`, `getString()` The `getLong()` method returns microseconds since epoch (00:00:00 UTC, January 1, 1970).
`TT_TIMESTAMP`	`getLong()`, `getString()` The `getLong()` method returns microseconds since epoch (00:00:00 UTC, January 1, 1970).
`ORA_DATE`	`getLong()`, `getString()` The `getLong()` method returns microseconds since epoch (00:00:00 UTC, January 1, 1970).
`ORA_TIMESTAMP`	`getLong()`, `getString()` The `getLong()` method returns microseconds since epoch (00:00:00 UTC, January 1, 1970). It truncates nanoseconds. Use `getString()` if you require nanosecond precision.
`TT_BINARY`	`getBytes()`
`TT_VARBINARY`	`getBytes()`
`ROWID`	`getBytes()`, `getString()`
`BLOB`	`getBytes()` Note: Information about the LOB value itself is unavailable. LOB fields contain zero-length data or null data (if the value is actually `NULL`).
`CLOB`, `NCLOB`	`getString()` Note: Information about the LOB value itself is unavailable. LOB fields contain zero-length data or null data (if the value is actually `NULL`).

Data Types Character Set

JMS/XLA uses a UTF-16 character set for specific data types.

TT_CHAR
TT_VARCHAR
ORA_CHAR
ORA_VARCHAR2
TT_NCHAR
TT_NVARCHAR
ORA_NCHAR
ORA_NVARCHAR2
NCHAR
NVARCHAR
NVARCHAR2