Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 7 Mar 2014 22:45:46 +0000 (UTC)
From: "Mamta A. Satoor (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12671616.1380645835060.26677.1394232346465@arcas>
In-Reply-To: <JIRA.12671616.1380645835060@arcas>
References: <JIRA.12671616.1380645835060@arcas>
Subject: [jira] [Commented] (DERBY-6361) Valid statements rejected if Derby
 has not implicitly created the current user's schema.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mamta A. Satoor commented on DERBY-6361:
----------------------------------------

Issue appears to be with lang/build.xml in 10.10 because that build.xml does not compile any test in lang directory with jdk1.6.

In trunk, all the lang tests get compiled with jdk1.6 and hence DatabaseMetadData.getSchemas(String, String) call(which was introduced in jdk 1.6) gets compiled correctly in trunk.

I am working on changing the build.xml in 10.10 lang directory to allow GeneratedColumnsTest.java to be compiled with jdk1.6 so we will not throw a compile time error for DatabaseMetadData.getSchemas(String, String) call made by the new junit fixture in GeneratedColumnsTest.java 

> Valid statements rejected if Derby has not implicitly created the current user's schema.
> ----------------------------------------------------------------------------------------
>
>                 Key: DERBY-6361
>                 URL: https://issues.apache.org/jira/browse/DERBY-6361
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>            Reporter: Rick Hillegas
>            Assignee: Mamta A. Satoor
>             Fix For: 10.11.0.0
>
>         Attachments: d6361-ignore-missing-schema.diff, derby-6361-01-aa-createDefaultSchema.diff
>
>
> There are many examples of statements failing because Derby has not implicitly created the schema associated with the current user. You don't see this if the schema is the default APP schema. But if the user is anyone other than APP, then various statements can fail. Maybe we should implicitly create a schema even if the user isn't APP. Right now, you get an error like this:
> ERROR 42Y07: Schema 'ROOT' does not exist
> The following script shows an example of this problem:
> connect 'jdbc:derby:memory:db;create=true;user=esq';
> create table licreq( domain varchar( 10 ) );
> connect 'jdbc:derby:memory:db;user=root';
> -- fails
> ALTER TABLE esq.licreq ADD COLUMN u_domain GENERATED ALWAYS AS (UPPER(domain));
> connect 'jdbc:derby:memory:db;user=app';
> -- succeeds
> ALTER TABLE esq.licreq ADD COLUMN u_domain GENERATED ALWAYS AS (UPPER(domain));


--
This message was sent by Atlassian JIRA
(v6.2#6252)