hi, yuan, The reason for HEX displaying is it can display all character correctly, for example Chinese character, in any terminal, or any encoding settings. For example, the terminal is using UTF8, but the source is encoded in GBK, if not display in HEX, the terminal will show unreadable characters, even harder to know what is the real source. It is rather difficult to read, but it is a safe way to display. One can develop tools to further interpret the HEX if needed, but the SQL engine should not bother to do this displaying thing IMHO.
thanks, Ming From: Liu, Yuan (Yuan) [mailto:yuan....@esgyn.cn] Sent: Friday, August 04, 2017 3:22 PM To: user@trafodion.incubator.apache.org Subject: Error 8413 shows source hex value? Hi Trafodioneers, Sometimes we may have 8413 error, error message is as below, [Error Code: -8413, SQL State: 22007] *** ERROR[8413] The string argument contains characters that cannot be converted. Source data(in hex): 6c655f31343739313937313833393837383038 [2017-08-04 14:21:24] I am wondering why the source data is shown as hex value which is hard to read. So I am suggesting that could we show the original character value here? Best regards, Yuan
