Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0AE8210F36 for ; Tue, 11 Mar 2014 18:18:02 +0000 (UTC) Received: (qmail 46077 invoked by uid 500); 11 Mar 2014 18:17:53 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 45879 invoked by uid 500); 11 Mar 2014 18:17:50 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 45699 invoked by uid 99); 11 Mar 2014 18:17:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Mar 2014 18:17:48 +0000 Date: Tue, 11 Mar 2014 18:17:48 +0000 (UTC) From: "Mamta A. Satoor (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor updated DERBY-6361: ----------------------------------- Fix Version/s: 10.8.3.3 > 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.8.3.3, 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)