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 4FC1711FF0 for ; Tue, 15 Jul 2014 17:43:06 +0000 (UTC) Received: (qmail 76584 invoked by uid 500); 15 Jul 2014 17:43:06 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 76563 invoked by uid 500); 15 Jul 2014 17:43:06 -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 76548 invoked by uid 99); 15 Jul 2014 17:43:06 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jul 2014 17:43:06 +0000 Date: Tue, 15 Jul 2014 17:43:06 +0000 (UTC) From: "Mike Matrigali (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DERBY-6664) Schema 'null' does not exist when trigger inserts into table with deferred foreign key 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-6664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062387#comment-14062387 ] Mike Matrigali commented on DERBY-6664: --------------------------------------- wondering if we should hold release for this fix, ie, make it a blocker? What will happen if users get the "bad" data on disk. What will users have to do once they get software with the fix. Will they have to manually drop/recreate? > Schema 'null' does not exist when trigger inserts into table with deferred foreign key > -------------------------------------------------------------------------------------- > > Key: DERBY-6664 > URL: https://issues.apache.org/jira/browse/DERBY-6664 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.11.0.0 > Reporter: Knut Anders Hatlen > Assignee: Knut Anders Hatlen > Attachments: d6664-1a.diff > > > If you modify the repro attached to DERBY-6663 so that the foreign key constraint TREF is INITIALLY DEFERRED, the final insert statement will fail like this: > {noformat} > ij> insert into othertable values 1; > ERROR 42Y07: Schema 'null' does not exist > {noformat} > I think the fix will be similar to DERBY-6663. FKInfo needs to store its schemaName field. -- This message was sent by Atlassian JIRA (v6.2#6252)