[ 
https://issues.apache.org/jira/browse/DERBY-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504256
 ] 

Tomohito Nakayama commented on DERBY-2705:
------------------------------------------

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 ...

> Description of error message for X0X61/X0Y59/X0Y69/X0Y70 in SQL error 
> messages and exceptions of Reference manual is not appropriate.
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2705
>                 URL: https://issues.apache.org/jira/browse/DERBY-2705
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>         Environment: 
> http://db.apache.org/derby/docs/dev/ref/rrefexcept71493.html
>            Reporter: Tomohito Nakayama
>
> 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. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to