Derby
  1. Derby
  2. DERBY-2705

Description of error message for X0X61/X0Y59/X0Y69/X0Y70 in SQL error messages and exceptions of Reference manual is not appropriate.

    Details

      Description

      I think positions of several words are not right.

      X0X61:
      The values for column '<location>' in index '<columnName>' and table '<indexName>.<schemaNamet>' do not match for row location <tableName>. The value in the index is '<value>', while the value in the base table is '<value>'. The full index key, including the row location, is '<indexKey>'. The suggested corrective action is to recreate the index.

      Corrected to :

      The values for column '<columnName>' in index '<indexName>' and table '<schemaNamet>.<tableName>' do not match for row location <location>. The value in the index is '<value>', while the value in the base table is '<value>'. The full index key, including the row location, is '<indexKey>'. The suggested corrective action is to recreate the index.

      X0Y59 :

      Attempt to add or enable constraint(s) on table '<rowName>' failed because the table contains <constraintName> row(s) that violate the following check constraint(s): <tableName>.

      Corrected to :

      Attempt to add or enable constraint(s) on table '<tableName>' failed because the table contains <rowName> row(s) that violate the following check constraint(s): <constraintName>.

      X0Y69 :
      <triggerName> is not supported in trigger <value>.

      Corrected to :

      <value> is not supported in trigger <triggerName>.

      X0Y70 :
      INSERT, UPDATE and DELETE are not permitted on table <triggerName> because trigger <tableName> is active.

      Corrected to

      INSERT, UPDATE and DELETE are not permitted on table <tableName> because trigger <triggerName> is active.

        Issue Links

          Activity

          Hide
          Knut Anders Hatlen added a comment -

          [bulk update] Close all resolved issues that haven't been updated for more than one year.

          Show
          Knut Anders Hatlen added a comment - [bulk update] Close all resolved issues that haven't been updated for more than one year.
          Hide
          Rick Hillegas added a comment -

          Attaching derby-2705-01-aa-latestGeneratedErrorTables.diff. This checks in the latest version of the generated documentation on error messages. It appears to me that all of the out-of-order argument names were addressed by the work on DERBY-5885. Committed at subversion revision 1414690.

          Touches the following file:

          M src/ref/rrefexcept71493.dita

          Show
          Rick Hillegas added a comment - Attaching derby-2705-01-aa-latestGeneratedErrorTables.diff. This checks in the latest version of the generated documentation on error messages. It appears to me that all of the out-of-order argument names were addressed by the work on DERBY-5885 . Committed at subversion revision 1414690. Touches the following file: M src/ref/rrefexcept71493.dita
          Hide
          Tomohito Nakayama added a comment -

          I think contents of arg element in message.xml are mistaken and
          others are correct.

          Show
          Tomohito Nakayama added a comment - I think contents of arg element in message.xml are mistaken and others are correct.
          Hide
          Tomohito Nakayama added a comment -

          Oops.
          I missed some informations ....

          I post again.

          contents in messages.xml :
          <msg>
          <name>X0X61.S</name>
          <text>The values for column '

          {4}

          ' in index '

          {0}' and table '{1}.{2}' do not match for row location {3}. The value in the index is '{5}', while the value in the base table is '{6}'. The full index key, including the row location, is '{7}'. The suggested corrective action is to recreate the index.</text>
          <arg>columnName</arg>
          <arg>indexName</arg>
          <arg>schemaNamet</arg>
          <arg>tableName</arg>
          <arg>location</arg>
          <arg>value</arg>
          <arg>value</arg>
          <arg>indexKey</arg>
          </msg>

          <msg>
          <name>X0Y59.S</name>
          <text>Attempt to add or enable constraint(s) on table '{1}' failed because the table contains {2} row(s) that violate the following check constraint(s): {0}

          .</text>
          <arg>tableName</arg>
          <arg>rowName</arg>
          <arg>constraintName</arg>
          </msg>

          <msg>
          <name>X0Y69.S</name>
          <text>

          {1} is not supported in trigger {0}.</text>
          <arg>value</arg>
          <arg>triggerName</arg>
          </msg>

          <msg>
          <name>X0Y70.S</name>
          <text>INSERT, UPDATE and DELETE are not permitted on table {1}

          because trigger

          {0}

          is active.</text>
          <arg>tableName</arg>
          <arg>triggerName</arg>
          </msg>

          lines in SQLState.java :
          String LANG_INDEX_COLUMN_NOT_EQUAL = "X0X61.S";
          String LANG_ADD_CHECK_CONSTRAINT_FAILED = "X0Y59.S";
          String LANG_NO_DDL_IN_TRIGGER = "X0Y69.S";
          String LANG_NO_DML_IN_TRIGGER = "X0Y70.S";

          codes to generate error messages :

          java/engine/org/apache/derby/iapi/db/ConsistencyChecker.java:356
          throw StandardException.newException(
          SQLState.LANG_INDEX_COLUMN_NOT_EQUAL,
          indexCD.getConglomerateName(),
          td.getSchemaName(),
          td.getName(),
          baseRL.toString(),
          cd.getColumnName(),
          indexColumn.toString(),
          baseColumn.toString(),
          indexRow.toString());

          java/shared/org/apache/derby/shared/common/reference/SQLState.java:1281
          if (isCheckConstraint)
          throw StandardException.newException(SQLState.LANG_ADD_CHECK_CONSTRAINT_FAILED,
          constraintName, td.getQualifiedName(), value.toString());

          java/engine/org/apache/derby/impl/sql/execute/InternalTriggerExecutionContext.java:338
          throw StandardException.newException(SQLState.LANG_NO_DDL_IN_TRIGGER, triggerd.getName(), constantAction.toString());

          Show
          Tomohito Nakayama added a comment - Oops. I missed some informations .... I post again. contents in messages.xml : <msg> <name>X0X61.S</name> <text>The values for column ' {4} ' in index ' {0}' and table '{1}.{2}' do not match for row location {3}. The value in the index is '{5}', while the value in the base table is '{6}'. The full index key, including the row location, is '{7}'. The suggested corrective action is to recreate the index.</text> <arg>columnName</arg> <arg>indexName</arg> <arg>schemaNamet</arg> <arg>tableName</arg> <arg>location</arg> <arg>value</arg> <arg>value</arg> <arg>indexKey</arg> </msg> <msg> <name>X0Y59.S</name> <text>Attempt to add or enable constraint(s) on table '{1}' failed because the table contains {2} row(s) that violate the following check constraint(s): {0} .</text> <arg>tableName</arg> <arg>rowName</arg> <arg>constraintName</arg> </msg> <msg> <name>X0Y69.S</name> <text> {1} is not supported in trigger {0}.</text> <arg>value</arg> <arg>triggerName</arg> </msg> <msg> <name>X0Y70.S</name> <text>INSERT, UPDATE and DELETE are not permitted on table {1} because trigger {0} is active.</text> <arg>tableName</arg> <arg>triggerName</arg> </msg> lines in SQLState.java : String LANG_INDEX_COLUMN_NOT_EQUAL = "X0X61.S"; String LANG_ADD_CHECK_CONSTRAINT_FAILED = "X0Y59.S"; String LANG_NO_DDL_IN_TRIGGER = "X0Y69.S"; String LANG_NO_DML_IN_TRIGGER = "X0Y70.S"; codes to generate error messages : java/engine/org/apache/derby/iapi/db/ConsistencyChecker.java:356 throw StandardException.newException( SQLState.LANG_INDEX_COLUMN_NOT_EQUAL, indexCD.getConglomerateName(), td.getSchemaName(), td.getName(), baseRL.toString(), cd.getColumnName(), indexColumn.toString(), baseColumn.toString(), indexRow.toString()); java/shared/org/apache/derby/shared/common/reference/SQLState.java:1281 if (isCheckConstraint) throw StandardException.newException(SQLState.LANG_ADD_CHECK_CONSTRAINT_FAILED, constraintName, td.getQualifiedName(), value.toString()); java/engine/org/apache/derby/impl/sql/execute/InternalTriggerExecutionContext.java:338 throw StandardException.newException(SQLState.LANG_NO_DDL_IN_TRIGGER, triggerd.getName(), constantAction.toString());
          Hide
          Tomohito Nakayama added a comment -

          I found next codes in source files.

          lines in SQLState.java :
          String LANG_INDEX_COLUMN_NOT_EQUAL = "X0X61.S";
          String LANG_ADD_CHECK_CONSTRAINT_FAILED = "X0Y59.S";
          String LANG_NO_DML_IN_TRIGGER = "X0Y70.S";

          codes to generate error messages :

          java/engine/org/apache/derby/iapi/db/ConsistencyChecker.java:356
          throw StandardException.newException(
          SQLState.LANG_INDEX_COLUMN_NOT_EQUAL,
          indexCD.getConglomerateName(),
          td.getSchemaName(),
          td.getName(),
          baseRL.toString(),
          cd.getColumnName(),
          indexColumn.toString(),
          baseColumn.toString(),
          indexRow.toString());

          java/shared/org/apache/derby/shared/common/reference/SQLState.java:1281
          if (isCheckConstraint)
          throw StandardException.newException(SQLState.LANG_ADD_CHECK_CONSTRAINT_FAILED,
          constraintName, td.getQualifiedName(), value.toString());

          I could not find code to generate error message for LANG_NO_DML_IN_TRIGGER ...

          Show
          Tomohito Nakayama added a comment - I found next codes in source files. lines in SQLState.java : String LANG_INDEX_COLUMN_NOT_EQUAL = "X0X61.S"; String LANG_ADD_CHECK_CONSTRAINT_FAILED = "X0Y59.S"; String LANG_NO_DML_IN_TRIGGER = "X0Y70.S"; codes to generate error messages : java/engine/org/apache/derby/iapi/db/ConsistencyChecker.java:356 throw StandardException.newException( SQLState.LANG_INDEX_COLUMN_NOT_EQUAL, indexCD.getConglomerateName(), td.getSchemaName(), td.getName(), baseRL.toString(), cd.getColumnName(), indexColumn.toString(), baseColumn.toString(), indexRow.toString()); java/shared/org/apache/derby/shared/common/reference/SQLState.java:1281 if (isCheckConstraint) throw StandardException.newException(SQLState.LANG_ADD_CHECK_CONSTRAINT_FAILED, constraintName, td.getQualifiedName(), value.toString()); I could not find code to generate error message for LANG_NO_DML_IN_TRIGGER ...
          Hide
          Tomohito Nakayama added a comment -

          I found next contents in java/engine/org/apache/derby/loc/messages.xml

          <msg>
          <name>X0X61.S</name>
          <text>The values for column '

          {4}

          ' in index '

          {0}' and table '{1}.{2}' do not match for row location {3}. The value in the index is '{5}', while the value in the base table is '{6}'. The full index key, including the row location, is '{7}'. The suggested corrective action is to recreate the index.</text>
          <arg>columnName</arg>
          <arg>indexName</arg>
          <arg>schemaNamet</arg>
          <arg>tableName</arg>
          <arg>location</arg>
          <arg>value</arg>
          <arg>value</arg>
          <arg>indexKey</arg>
          </msg>


          <msg>
          <name>X0Y69.S</name>
          <text>{1} is not supported in trigger {0}

          .</text>
          <arg>value</arg>
          <arg>triggerName</arg>
          </msg>

          <msg>
          <name>X0Y70.S</name>
          <text>INSERT, UPDATE and DELETE are not permitted on table

          {1}

          because trigger

          {0}

          is active.</text>
          <arg>tableName</arg>
          <arg>triggerName</arg>
          </msg>

          Hmm ... :I

          Show
          Tomohito Nakayama added a comment - I found next contents in java/engine/org/apache/derby/loc/messages.xml <msg> <name>X0X61.S</name> <text>The values for column ' {4} ' in index ' {0}' and table '{1}.{2}' do not match for row location {3}. The value in the index is '{5}', while the value in the base table is '{6}'. The full index key, including the row location, is '{7}'. The suggested corrective action is to recreate the index.</text> <arg>columnName</arg> <arg>indexName</arg> <arg>schemaNamet</arg> <arg>tableName</arg> <arg>location</arg> <arg>value</arg> <arg>value</arg> <arg>indexKey</arg> </msg> <msg> <name>X0Y69.S</name> <text>{1} is not supported in trigger {0} .</text> <arg>value</arg> <arg>triggerName</arg> </msg> <msg> <name>X0Y70.S</name> <text>INSERT, UPDATE and DELETE are not permitted on table {1} because trigger {0} is active.</text> <arg>tableName</arg> <arg>triggerName</arg> </msg> Hmm ... :I
          Hide
          Tomohito Nakayama added a comment -

          Not sure yet ....
          Reading messages of program translated to Japanese,
          I came to suspect both.

          I will survery.

          Show
          Tomohito Nakayama added a comment - Not sure yet .... Reading messages of program translated to Japanese, I came to suspect both. I will survery.
          Hide
          Laura Stewart added a comment -

          Tomohito - Are the descriptions only incorrect in the Ref Manual or in the code as well?

          Show
          Laura Stewart added a comment - Tomohito - Are the descriptions only incorrect in the Ref Manual or in the code as well?
          Hide
          Tomohito Nakayama added a comment -

          I updated description of this issue to add X0Y59/X0Y69/X0Y70.

          Show
          Tomohito Nakayama added a comment - I updated description of this issue to add X0Y59/X0Y69/X0Y70.
          Hide
          Tomohito Nakayama added a comment -

          Sorry.
          I took wrong X0Y70 and X0Y69 in previous EDIT.

          X0Y70 :
          INSERT, UPDATE and DELETE are not permitted on table <triggerName> because trigger <tableName> is active.

          This should be

          INSERT, UPDATE and DELETE are not permitted on table <tableName> because trigger <triggerName> is active.

          X0Y69 :
          Same as previous comment.

          Show
          Tomohito Nakayama added a comment - Sorry. I took wrong X0Y70 and X0Y69 in previous EDIT. X0Y70 : INSERT, UPDATE and DELETE are not permitted on table <triggerName> because trigger <tableName> is active. This should be INSERT, UPDATE and DELETE are not permitted on table <tableName> because trigger <triggerName> is active. X0Y69 : Same as previous comment.
          Hide
          Tomohito Nakayama added a comment -

          I think X0Y70 have resembling problem.

          <triggerName> is not supported in trigger <value>.

          I think correct description is next.
          <value> is not supported in trigger <triggerName>.

          Show
          Tomohito Nakayama added a comment - I think X0Y70 have resembling problem. <triggerName> is not supported in trigger <value>. I think correct description is next. <value> is not supported in trigger <triggerName>.
          Hide
          Tomohito Nakayama added a comment -

          In X0Y59, I think <rowName> is <rowCount>.

          Show
          Tomohito Nakayama added a comment - In X0Y59, I think <rowName> is <rowCount>.
          Hide
          Tomohito Nakayama added a comment -

          Resembling problem exists in X0Y59 too.

          Attempt to add or enable constraint(s) on table '<rowName>' failed because the table contains <constraintName> row(s) that violate the following check constraint(s): <tableName>.

          The description should be
          Attempt to add or enable constraint(s) on table '<tableName>' failed because the table contains <rowName> row(s) that violate the following check constraint(s): <constraintName>.

          Show
          Tomohito Nakayama added a comment - Resembling problem exists in X0Y59 too. Attempt to add or enable constraint(s) on table '<rowName>' failed because the table contains <constraintName> row(s) that violate the following check constraint(s): <tableName>. The description should be Attempt to add or enable constraint(s) on table '<tableName>' failed because the table contains <rowName> row(s) that violate the following check constraint(s): <constraintName>.

            People

            • Assignee:
              Unassigned
              Reporter:
              Tomohito Nakayama
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development