[ http://issues.apache.org/jira/browse/DERBY-1612?page=comments#action_12425665 ] Daniel John Debrunner commented on DERBY-1612: ----------------------------------------------
Ok - thanks for the additional info, looking further I see the DROP_INDEX invalidation will be sent and so compiled plans that are dependent on that index will be re-compiled, that's what I was concerned about. The information you gathered is useful to add somewhere as a comment, maybe for the constant DROP_CONSTRAINT, as by its name alone I would assume it is sent out for all drop constraints. I'll commit the patch. > As per the functional spec attached to DERBY-1330, a constraint should be > dropped when a privilege required by the constraint is revoked. > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1612 > URL: http://issues.apache.org/jira/browse/DERBY-1612 > Project: Derby > Issue Type: New Feature > Components: SQL > Affects Versions: 10.2.0.0 > Reporter: Mamta A. Satoor > Assigned To: Mamta A. Satoor > Fix For: 10.2.0.0 > > Attachments: DERBY1612_V1_diff_DropConstraintOnRevoke.txt, > DERBY1612_V1_stat_DropConstraintOnRevoke.txt > > > A constraint tracks its privileges requirements using Derby's Dependency > Manager. If any one of those required privileges are revoked, the constraint > should be dropped automatically. > I am just creating a new jira entry here so it is easier to track sub items > of DERBY-1330. Will link this Jira entry to DERBY-1330. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
