Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <42A5B6A2.2010702@sbcglobal.net>
Date: Tue, 07 Jun 2005 08:00:50 -0700
From: Jack Klebanoff <klebanoff-derby@sbcglobal.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: [PATCH] Referential Constraints
References: <429DC906.10604@sbcglobal.net> <42A0DCDB.6050502@debrunners.com>
In-Reply-To: <42A0DCDB.6050502@debrunners.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Daniel John Debrunner wrote:

>Jack wrote:
>
>[snip]
>  
>
>>The patch changes iapi/sql/dictionary/DDUtils.java to remove the DDL time checks
>>    
>>
>[snip]
>
>I think all those checks need to remain for soft upgrade mode, otherwise
>your changes allow referential actions to be created that will not be
>handled correctly by 10.0 engines.
>
>The runtime code could probably remain as-is, in soft upgrade mode it
>would just handle cases that wouldn't exist. So only the DDL code would
>need checkVersion() calls.
>
>
>Dan.
>
>
>  
>
I have modified my patch to incorporate Dan's request. The new patch 
looks at the database version and applies the V10.0 checks during 
referential constraint DDL if the database is V10.0 (soft upgrade). The 
new patch is attached to Derby-338 
(http://issues.apache.org/jira/browse/DERBY-338).

Jack