[
https://issues.apache.org/jira/browse/TRAFODION-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335106#comment-15335106
]
liu ming commented on TRAFODION-1676:
-------------------------------------
should take care all these error code:
EXE_INVALID_DEFINE_CLASS_ERROR = 8400,
EXE_CARDINALITY_VIOLATION = 8401,
EXE_STRING_OVERFLOW = 8402,
EXE_SUBSTRING_ERROR = 8403,
EXE_TRIM_ERROR = 8404,
EXE_CONVERTTIMESTAMP_ERROR = 8405,
EXE_JULIANTIMESTAMP_ERROR = 8407,
EXE_INVALID_ESCAPE_CHARACTER = 8409,
EXE_INVALID_ESCAPE_SEQUENCE = 8410,
EXE_NUMERIC_OVERFLOW = 8411,
EXE_MISSING_NULL_TERMINATOR = 8412,
EXE_CONVERT_STRING_ERROR = 8413,
EXE_CONVERT_NOT_SUPPORTED = 8414,
EXE_CONVERT_DATETIME_ERROR = 8415,
EXE_DATETIME_FIELD_OVERFLOW = 8416,
EXE_USER_FUNCTION_ERROR = 8417,
EXE_USER_FUNCTION_NOT_SUPP = 8418,
EXE_DIVISION_BY_ZERO = 8419,
EXE_MISSING_INDICATOR_VARIABLE = 8420,
EXE_ASSIGNING_NULL_TO_NOT_NULL = 8421,
EXE_CONVERT_INTERVAL_ERROR = 8422,
EXE_FIELD_NUM_OVERFLOW = 8423,
EXE_MATH_FUNC_NOT_SUPPORTED = 8424,
EXE_DEFAULT_VALUE_ERROR = 8425,
EXE_SORT_ERROR = 8427,
EXE_BAD_ARG_TO_MATH_FUNC = 8428,
EXE_MAPPED_FUNCTION_ERROR = 8429,
EXE_GETBIT_ERROR = 8430,
EXE_IS_BITWISE_AND_ERROR = 8431,
EXE_UNSIGNED_OVERFLOW = 8432,
EXE_INVALID_CHARACTER = 8433,
EXE_HIVE_DATA_MOD_CHECK_ERROR = 8436,
EXE_HISTORY_BUFFER_TOO_SMALL = 8440,
EXE_OLAP_OVERFLOW_NOT_SUPPORTED = 8441,
EXE_ERROR_FROM_LOB_INTERFACE = 8442,
EXE_INVALID_LOB_HANDLE = 8443,
EXE_LAST_EXPRESSIONS_ERROR = 8499,
> 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)
