... |
* 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. |
* If [widenComparisonToString|System Properties] is false (the default), when Teiid detects that an explicit conversion can not be applied implicitly in criteria, then an exception will be raised. If [widenComparisonToString|System Properties] is true, then depending upon the comparison a widening conversion will be applied or 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: |
{code:SQL}SELECT * FROM my.table WHERE created_by = ‘'not a date’'{code} |
|
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. |
With [widenComparisonToString|System Properties] as false and created\_by is typed as date, rather than converting 'not a date' to a date value, an exception will be raised. |
|
* 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[]. |
* 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. |
... |
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:
For example:
SELECT * FROM my.table WHERE created_by = 'not a date'
With widenComparisonToString as false and created_by is typed as date, rather than converting 'not a date' to a date value, an exception will be raised.
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. |
Source Type | Valid Implicit Target Types | Valid Explicit Target Types |
---|---|---|
string | clob | char, boolean, byte, short, integer, long, biginteger, float, double, bigdecimal, xml [a] |
char | string | |
boolean | string, byte, short, integer, long, biginteger, float, double, bigdecimal | |
byte | string, short, integer, long, biginteger, float, double, bigdecimal | boolean |
short | string, integer, long, biginteger, float, double, bigdecimal | boolean, byte |
integer | string, long, biginteger, double, bigdecimal | boolean, byte, short, float |
long | string, biginteger, bigdecimal | boolean, byte, short, integer, float, double |
biginteger | string, bigdecimal | boolean, byte, short, integer, long, float, double |
bigdecimal | string | boolean, byte, short, integer, long, biginteger, float, double |
float | string, bigdecimal, double | boolean, byte, short, integer, long, biginteger |
double | string, bigdecimal | boolean, byte, short, integer, long, biginteger, float |
date | string, timestamp | |
time | string, timestamp | |
timestamp | string | date, time |
clob | string | |
xml | string [b] |
[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