Return-Path: 
 <derby-dev-return-44624-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 65237 invoked from network); 13 Jun 2007 14:39:48 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 13 Jun 2007 14:39:48 -0000
Received: (qmail 49734 invoked by uid 500); 13 Jun 2007 14:39:52 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 49508 invoked by uid 500); 13 Jun 2007 14:39:51 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:derby-dev-help@db.apache.org>
List-Unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 49499 invoked by uid 99); 13 Jun 2007 14:39:51 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2007 07:39:51 -0700
X-ASF-Spam-Status: No, hits=-100.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jun 2007 07:39:47 -0700
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 106227141AA
	for <derby-dev@db.apache.org>; Wed, 13 Jun 2007 07:39:27 -0700 (PDT)
Message-ID: <25873162.1181745567064.JavaMail.jira@brutus>
Date: Wed, 13 Jun 2007 07:39:27 -0700 (PDT)
From: "Tomohito Nakayama (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2705) Description of error message for
 X0X61/X0Y59/X0Y69/X0Y70 in SQL error messages and exceptions of Reference
 manual is not appropriate.
In-Reply-To: <5425157.1180245076409.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


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

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

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());


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