Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 7 Mar 2011 06:34:00 +0000 (UTC)
From: "Mamta A. Satoor (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <2092883937.429.1299479640508.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1199483292.5525.1299001237382.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (DERBY-5079) DERBY-4984 caused a regression which
 will not allow users to drop a table if the table was involved in a trigger
 action rebind during ALTER TABLE DROP COLUMN
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003278#comment-13003278 ] 

Mamta A. Satoor commented on DERBY-5079:
----------------------------------------

Fixed the problem in trunk. will work on migrating it to 10.7 next.

> DERBY-4984 caused a regression which will not allow users to drop a table if the table was involved in a trigger action rebind during ALTER TABLE DROP COLUMN
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5079
>                 URL: https://issues.apache.org/jira/browse/DERBY-5079
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.7.1.3, 10.8.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>            Priority: Blocker
>             Fix For: 10.8.0.0
>
>
> The fix for DERBY-4984 has introduced a regression which adds rows into SYSDEPENDS which are incorrect. The error I think was caused when before doing a rebind of trigger action, I made the trigger table as the current dependent in the dependency system and hence all the dependencies required by the trigger action got associated with that trigger table and hence causing the errorneous behavior. I will work on this asap. The fix went into trunk and 10.7. I will add a test case for this in the jira and will also add a test case in our junit test

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira