db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6361) Valid statements rejected if Derby has not implicitly created the current user's schema.
Date Mon, 10 Mar 2014 07:48:44 GMT

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

Knut Anders Hatlen commented on DERBY-6361:
-------------------------------------------

The changes in the backport seems to have broken the tests on Java 5, because the classes
cannot be loaded on that platform if they have been compiled with target level 1.6. I think
a better way to port the test case would be to make it use the getSchemas() method instead
of getSchemas(String,String), as the former is also available in earlier JDBC versions.

> 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.9.2.2, 10.10.1.4, 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)

Mime
View raw message