Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-2901

Improve error message triggered by selecting unknown column

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: Qserv
    • Labels:

      Description

      Selecting a column that does not exist, for example:

      SELECT nonExistingColumn 
      FROM Object
      

      Generates an obscure error message:

      ERROR 4120 (Proxy): Error during execution:
      -1 Ref=1 Resource(/chk/qservTest_case01_qserv/6630): 20150608-19:30:36, Error in result data., 1, 
      Ref=2 Resource(/chk/qservTest_case01_qserv/6631): 20150608-19:30:36, State error (unrecognized), 0, 
      Ref=3 Resource(/chk/qservTest_case01_qserv/6800): 20150608 (-1)
      

      This story involves changing the code so that we produce a more obvious error. BTW, MySQL will produce

      ERROR 1054 (42S22): Unknown column '<name here>' in 'field list'
      

        Attachments

          Issue Links

            Activity

            Hide
            fritzm Fritz Mueller added a comment -

            Done in course of tableref rework. Current error message, while not perfect, is acceptable:

            ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: analyzeQuery unexpected:Could not find a table ref match for ColumnRef("TableRef("", "", "")", "nonExistingColumn")

            Show
            fritzm Fritz Mueller added a comment - Done in course of tableref rework. Current error message, while not perfect, is acceptable: ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: analyzeQuery unexpected:Could not find a table ref match for ColumnRef("TableRef("", "", "")", "nonExistingColumn")

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              fritzm Fritz Mueller
              Watchers:
              Fritz Mueller
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.