Default Transform Behavior for UDT and CDT Data Values
The input UDT and CDT data values sent to the table operator are in their default transform form. This may correspond to either the SQL transform type of the UDT or another predefined type. The UDT and CDT values are converted to their corresponding transform type by invoking the default transform function defined for the UDT or CDT. The following table shows the transform types for UDT and CDT data types passed to a table operator.
This mode is well suited for a connector-type of operator (T2T or T2M) that does import and export of data values.
Note that some UDTs and CDTs (such as XML, ST_Geometry, DATASET, and JSON) support multiple transform groups. However, for table operators, the CDT values will always be sent using the default transform type. For instance, a JSON data value will always be sent as a CLOB.
SQL UDT or Complex Data Type | SQL Data Type Mapping | Java Data Type |
---|---|---|
ARRAY/ VARRAY | VARCHAR (the defined transform type) | java.lang.String |
BSON | BLOB or CLOB |
|
DATASET – Avro | BLOB | java.sql.Blob |
DATASET – CSV | CLOB | java.sql.Clob |
Geospatial – MBB | VARCHAR | java.lang.String |
Geospatial – MBR | VARCHAR | java.lang.String |
Geospatial – ST_Geometry | CLOB | java.sql.Clob |
JSON | CLOB | java.sql.Clob |
Period | VARCHAR | java.lang.String |
UDT (Distinct) | Predefined data type that the UDT is based on | Primitive Java data type For example:
|
UDT (Structured) | Predefined data type as defined in CREATE TRANSFORM | Primitive Java data type For example:
|
XML | CLOB | java.sql.Clob |