db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Created: (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
Date Tue, 01 Mar 2011 17:40:37 GMT
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


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

        

Mime
View raw message