Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 1 Oct 2013 16:45:23 +0000 (UTC)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12671616.1380645835060.11898.1380645923831@arcas>
In-Reply-To: <JIRA.12671616.1380645835060@arcas>
References: <JIRA.12671616.1380645835060@arcas>
Subject: [jira] [Created] (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

Rick Hillegas created DERBY-6361:
------------------------------------

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


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.1#6144)