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

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

Github user selvaganesang commented on a diff in the pull request:

    https://github.com/apache/trafodion/pull/1504#discussion_r179548743
  
    --- Diff: core/sql/bin/SqlciErrors.txt ---
    @@ -2,7 +2,7 @@
     1000 42000 99999 BEGINNER INFRM LOGONLY A syntax error occurred.
     1001 ZZZZZ 99999 ADVANCED CRTCL DIALOUT An internal error occurred in 
module $0~String0 on line $1~Int0. Details($2~String1).
     1002 ZZZZZ 99999 BEGINNER MAJOR DBADMIN Catalog $0~CatalogName does not 
exist.
    -1003 ZZZZZ 99999 BEGINNER MINOR DBADMIN Schema $0~SchemaName does not 
exist.
    +1003 ZZZZZ 99999 BEGINNER MINOR DBADMIN Schema $0~String0.$1~String1 does 
not exist.
    --- End diff --
    
    There are two ways to raise an error. 
    1) Using ExRaiseSqlError method passing in sqlcode, string and numeric 
parameters 
    2) concatenating SQLError code and the parameters via ComDiagsArea << 
DgSqlCode << DgStringParam0 or DgCatalogName etc.
    
    Option 1 doesn't support the concept of DgCatalogName or DgSchemaName .
    When an error needs to be populated in both ways, we had to change it to 
use String0 and String1 etc..


> Streamline error handling in Executor utility commands
> ------------------------------------------------------
>
>                 Key: TRAFODION-3009
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-3009
>             Project: Apache Trafodion
>          Issue Type: Improvement
>          Components: -exe, sql-exe
>            Reporter: Selvaganesan Govindarajan
>            Assignee: Selvaganesan Govindarajan
>            Priority: Major
>
> Executor utility commands are the commands that issue sql statements during 
> its execution to complete its task. These operators are  derived from 
> ExExeUtilTcb operator in Trafodion.  These commands assume ComDiagsArea is 
> allocated in advance. This is not in accordance with the design as outlined in
> [https://cwiki.apache.org/confluence/display/TRAFODION/SQL+Diagnostics+Architecture+and+Design]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to