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 5CEF91167B for ; Tue, 15 Jul 2014 19:15:07 +0000 (UTC) Received: (qmail 87636 invoked by uid 500); 15 Jul 2014 19:15:07 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 87565 invoked by uid 500); 15 Jul 2014 19:15: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 87381 invoked by uid 99); 15 Jul 2014 19:15: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 19:15:06 +0000 Date: Tue, 15 Jul 2014 19:15:06 +0000 (UTC) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DERBY-6661) dblook does not recognize the deferrability of deferrable constraints 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-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-6661: --------------------------------- Attachment: derby-6661-01-aa-recreateDeferrableConstraints.diff Attaching derby-6661-01-aa-recreateDeferrableConstraints.diff. This patch adds dblook support for deferrable constraints. I will run tests. Touches the following files: -------------- M java/tools/org/apache/derby/impl/tools/dblook/DB_Check.java M java/tools/org/apache/derby/impl/tools/dblook/DB_Key.java M java/engine/org/apache/derby/impl/sql/catalog/SYSCONSTRAINTSRowFactory.java Adds code to dblook to handle deferrable constraints. I had to clone some code in the DataDictionary because the code can't be shared today due to the way we factor Derby into jar files. We expect that dblook can be run client-side without an engine jar file. -------------- A java/testing/org/apache/derbyTesting/functionTests/tests/tools/Test_6661.java M java/testing/org/apache/derbyTesting/functionTests/tests/tools/dblook_test.java M java/testing/org/apache/derbyTesting/functionTests/tests/tools/_Suite.java Adds a test to verify that dblook correctly recreates deferrable primary, unique, foreign, and check constraints. > dblook does not recognize the deferrability of deferrable constraints > --------------------------------------------------------------------- > > Key: DERBY-6661 > URL: https://issues.apache.org/jira/browse/DERBY-6661 > Project: Derby > Issue Type: Bug > Components: Tools > Affects Versions: 10.11.0.0 > Reporter: Rick Hillegas > Assignee: Rick Hillegas > Attachments: derby-6661-01-aa-recreateDeferrableConstraints.diff > > > If you create a table with a deferrable primary key constraint and then run dblook, the recreation ddl does not flag the primary key as deferrable. I suspect that this applies to other kinds of constraints as well. -- This message was sent by Atlassian JIRA (v6.2#6252)