[ 
https://issues.apache.org/jira/browse/TRAFODION-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332936#comment-15332936
 ] 

ASF GitHub Bot commented on TRAFODION-1745:
-------------------------------------------

GitHub user traflm opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/547

    [TRAFODION-1745] show more related info when TRANSLATE run into SQL E…

    …rror
    
    Show what is the translation: from which charset to what charset, and 
showing the offending data in HEX mode.
    This will help troubleshooting.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/traflm/incubator-trafodion TRAFODION-2046-1

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/547.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #547
    
----
commit 4934fdec0bc98aa037db5793366ab8600e544f58
Author: Liu Ming <ovis_p...@sina.com>
Date:   2016-06-16T02:17:18Z

    [TRAFODION-1745] show more related info when TRANSLATE run into SQL Error

----


> show more related info when TRANSLATE run into SQL Error
> --------------------------------------------------------
>
>                 Key: TRAFODION-1745
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1745
>             Project: Apache Trafodion
>          Issue Type: Improvement
>            Reporter: liu ming
>            Assignee: liu ming
>
> The current error message for a TRANSLATE error can be :
> 8690 "An invalid character value encountered in TRANSLATE function."
> Need to show more helping info for easier debug, and user friendly.
> to include a short section of offending source data (may be in hex form), 
> source charset, and target charset.
> Checking other SQL errors related if possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to