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: <1029398848.1117003854625.JavaMail.jira@ajax.apache.org>
Date: Wed, 25 May 2005 08:50:54 +0200 (CEST)
From: "Shreyas Kaushik (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-12) Quoted table names mishandled in select
 list expansion
In-Reply-To: <630187231.1096483772196.JavaMail.apache@nagoya>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-12?page=all ]
     
Shreyas Kaushik resolved DERBY-12:
----------------------------------

    Resolution: Fixed

This has been fixed as per the patch I submitted for Derby - 12 and Derby -13. All the test cases that the bug description says behave as expected.

> Quoted table names mishandled in select list expansion
> ------------------------------------------------------
>
>          Key: DERBY-12
>          URL: http://issues.apache.org/jira/browse/DERBY-12
>      Project: Derby
>         Type: Bug
>   Components: SQL
>     Versions: 10.0.2.0
>     Reporter: Ramandeep Kaur
>     Priority: Minor

>
> Opening this bug on behalf of Satheesh Bandaram.
> ------------------------------------------------------
> Select list expansion is incorrect when there is a quoted table 
> name with an embedded period. Consider the following SQL:
>   create table "S1.T1" (id int not null primary key, d1 int);
>   create schema s1;
>   create table s1.t1 (id int not null primary key, d2 int);
>   select s1.t1.* from "S1.T1";
>   select "S1.T1".* from s1.t1;
> The select statements should both throw errors, because s1.t1 
> and "S1.T1" are different tables. However Derby does not 
> throw an error. However, the following SQL does throw an error, 
> as it should.
>   select "S1.T1".id from s1.t1;
>   select s1.t1.id from "S1.T1"

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