Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <705607926.1117176116402.JavaMail.jira@ajax.apache.org>
Date: Fri, 27 May 2005 08:41:56 +0200 (CEST)
From: "Samuel Andrew McIntyre (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Assigned: (DERBY-180) XCL47 SQLState duplicated in
 messages_en.properties?
In-Reply-To: <1464388014.1111698982852.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-180?page=all ]

Samuel Andrew McIntyre reassigned DERBY-180:
--------------------------------------------

    Assign To: Samuel Andrew McIntyre

> XCL47 SQLState duplicated in messages_en.properties?
> ----------------------------------------------------
>
>          Key: DERBY-180
>          URL: http://issues.apache.org/jira/browse/DERBY-180
>      Project: Derby
>         Type: Bug
>   Components: SQL
>     Versions: 10.0.2.0
>  Environment: Windows XP SP1 Professional
>     Reporter: George Baklarz
>     Assignee: Samuel Andrew McIntyre
>     Priority: Minor

>
> In the messages_en.properties file, there are two items that are similar:
> XCL47.S=Use of ''{0}'' requires database to be upgraded from version {1} to version {2} or later.
> XCL478.S=The requested function can not reference tables in SESSION schema.
> SQLSTATEs are supposed to be 5 characters long. When I issue a CREATE VIEW on a SESSION table, I receive the proper error message:
> ij> declare global temporary table x (a int) not logged;
> 0 rows inserted/updated/deleted
> ij> create view z as (select * from session.x);
> ERROR XCL47: The requested function can not reference tables in SESSION schema.
> So, was XCL478 truncated to XCL47? Does this mean that if I tried to do something that invokes the other version of XCL47 that I will get the wrong message? I suspect one of the message numbers needs to be changed and that the SQL error be fixed to be 5 characters long instead of 6.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira