Data types may be converted from one form to another either explicitly or implicitly. Implicit conversions automatically occur in criteria and expressions to ease development. Explicit datatype conversions require the use of the CONVERT function or CAST keyword.

Type Conversion Considerations:

• Any type may be implicitly converted to the OBJECT type.

• The OBJECT type may be explicitly converted to any other type.

• The NULL value may be converted to any type.

• Any valid implicit conversion is also a valid explicit conversion.

• Situations involving literal values that would normally require explicit conversions may have the explicit conversion applied implicitly if no loss of information occurs.

• When Teiid detects that an explicit conversion can not be applied implicitly in criteria, the criteria will be treated as false.

• Array conversions are currently only valid to and from compatible object arrays. It is not yet possible for example to cast from integer[] to long[].

For example:

SELECT * FROM my.table WHERE created_by = ‘not a date’

Given that created_by is typed as date, rather than converting 'not a date' to a date value, the criteria will remain as a string comparison and therefore be false.

• Explicit conversions that are not allowed between two types will result in an exception before execution. Allowed explicit conversions may still fail during processing if the runtime values are not actually convertable.

Warning The Teiid conversions of float/double/bigdecimal/timestamp to string rely on the JDBC/Java defined output formats. Pushdown behavior attempts to mimic these results, but may vary depending upon the actual source type and conversion logic. Care should be taken to not assume the string form in criteria or other places where a variation may cause different results.

[a] string to xml is equivalent to XMLPARSE(DOCUMENT exp) - See also XML Functions#XMLPARSE
[b] xml to string is equivalent to XMLSERIALIZE(exp AS STRING) - see also XML Functions#XMLSERIALIZE