[
https://issues.apache.org/jira/browse/TRAFODION-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362591#comment-15362591
]
liu ming commented on TRAFODION-1676:
-------------------------------------
This PR (564) enhance error messages for these SQL Errors:
EXE_CONVERTTIMESTAMP_ERROR = 8405,
EXE_JULIANTIMESTAMP_ERROR = 8407,
EXE_CONVERT_STRING_ERROR = 8413
EXE_CONVERT_DATETIME_ERROR = 8415,
By displaying the offending source data content, for CONVERT_STRING_ERROR,
because it always contains multi-byte character, so display the data in HEX
mode.
> support better runtime error message when a SQL function meet fital error
> -------------------------------------------------------------------------
>
> Key: TRAFODION-1676
> URL: https://issues.apache.org/jira/browse/TRAFODION-1676
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: sql-exe
> Reporter: liu ming
> Assignee: liu ming
> Priority: Minor
>
> A sql contains some SQL function, for example UPPER(), when the input data of
> UPPER() contains invalid data, UPPER() will fail. In this case, the whole
> query abort, and the error message cannot tell which row has invalid data, so
> it is very hard to fix the problem.
> It will be good to have row id or the real value of the error row in the
> error message to help trouble shooting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
