Red Hat Training

A Red Hat training course is available for Red Hat JBoss Data Virtualization

Chapter 4. Data Types

4.1. Supported Types

JBoss Data Virtualization supports a core set of runtime types. Runtime types can be different from semantic types defined in type fields at design time. The runtime type can also be specified at design time or it will be automatically chosen as the closest base type to the semantic type.

Table 4.1. JBoss Data Virtualization Runtime Types

Type Description Java Runtime Class JDBC Type ODBC Type
string or varchar variable length character string with a maximum length of 4000. Note that the length cannot be explicitly set with the type declaration, e.g. varchar(100) is invalid. java.lang.String VARCHAR VARCHAR
varbinary variable length binary string with a maximum length of 8192. Note that the length cannot be explicitly set with the type declaration, e.g. varbinary(100) is invalid. byte[] [a] VARBINARY VARBINARY
char a single Unicode character java.lang.Character CHAR CHAR
boolean a single bit, or Boolean, that can be true, false, or null (unknown) java.lang.Boolean BIT SMALLINT
byte or tinyint numeric, integral type, signed 8-bit java.lang.Byte TINYINT SMALLINT
short or smallint numeric, integral type, signed 16-bit java.lang.Short SMALLINT SMALLINT
integer or serial numeric, integral type, signed 32-bit. The serial type also implies not null and has an auto-incrementing value that starts at 1. Serial types are not automatically UNIQUE. java.lang.Integer INTEGER INTEGER
long or bigint numeric, integral type, signed 64-bit java.lang.Long BIGINT NUMERIC
biginteger numeric, integral type, arbitrary precision of up to 1000 digits java.math.BigInteger NUMERIC NUMERIC
float or real numeric, floating point type, 32-bit IEEE 754 floating-point numbers java.lang.Float REAL FLOAT
double numeric, floating point type, 64-bit IEEE 754 floating-point numbers java.lang.Double DOUBLE DOUBLE
bigdecimal or decimal numeric, floating point type, arbitrary precision of up to 1000 digits. Note that the precision and scale cannot be explicitly set with the type literal, e.g. decimal(38, 2). java.math.BigDecimal NUMERIC NUMERIC
date datetime, representing a single day (year, month, day) java.sql.Date DATE DATE
time datetime, representing a single time (hours, minutes, seconds, milliseconds) java.sql.Time TIME TIME
timestamp datetime, representing a single date and time (year, month, day, hours, minutes, seconds, milliseconds, nanoseconds) java.sql.Timestamp TIMESTAMP TIMESTAMP
object any arbitrary Java object, must implement java.lang.Serializable Any JAVA_OBJECT VARCHAR
blob binary large object, representing a stream of bytes java.sql.Blob [b] BLOB VARCHAR
clob character large object, representing a stream of characters java.sql.Clob [c] CLOB VARCHAR
xml XML document java.sql.SQLXML [d] JAVA_OBJECT VARCHAR
geometry Geospatial Object java.sql.Blob [e] BLOB BLOB
[a] The runtime type is org.teiid.core.types.BinaryType. Translators will need to explicitly handle BinaryType values. UDFs will instead have a byte[] value passed.
[b] The concrete type is expected to be org.teiid.core.types.BlobType
[c] The concrete type is expected to be org.teiid.core.types.ClobType
[d] The concrete type is expected to be org.teiid.core.types.XMLType
[e] The concrete type is expected to be org.teiid.core.types.GeometryType