Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 16148 invoked from network); 1 Aug 2006 16:20:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Aug 2006 16:20:47 -0000 Received: (qmail 61539 invoked by uid 500); 1 Aug 2006 16:20:46 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 61500 invoked by uid 500); 1 Aug 2006 16:20:46 -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 61491 invoked by uid 99); 1 Aug 2006 16:20:46 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Aug 2006 09:20:46 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Aug 2006 09:20:46 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CA8A6410017 for ; Tue, 1 Aug 2006 16:18:14 +0000 (GMT) Message-ID: <28986898.1154449094827.JavaMail.jira@brutus> Date: Tue, 1 Aug 2006 09:18:14 -0700 (PDT) From: "Daniel John Debrunner (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-1539) As per the functional spec attached to DERBY-1330, a trigger should be dropped when a privilege required by the trigger is revoked. In-Reply-To: <13235269.1153345754042.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-1539?page=comments#action_12424913 ] Daniel John Debrunner commented on DERBY-1539: ---------------------------------------------- On the trigger re-compile issue it seems there is a serious problem currently (regardless of grant/revoke issues) with triggers. This may need to be fixed before modifying the trigger -revoke interation any more. I wonder if you can make progress on the view & constraint dropping before completing the trigger? At least get them in to a similar state as triggers where a revoke wil drop the object, even if it drops it in too many situations. > As per the functional spec attached to DERBY-1330, a trigger should be dropped when a privilege required by the trigger is revoked. > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1539 > URL: http://issues.apache.org/jira/browse/DERBY-1539 > 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: DERBY1539V1hashCodeEqualsDiff.txt, DERBY1539V1hashCodeEqualsStat.txt, DERBY1539V2diffDropTriggerOnRevoke.txt, DERBY1539V2statDropTriggerOnRevoke.txt, DERBY1539V3diffDropTriggerOnRevoke.txt, DERBY1539V3statDropTriggerOnRevoke.txt, DERBY1539V4diffDropTriggerOnRevoke.txt, DERBY1539V4diffDropTriggerOnRevokeRequiredPrivilege.txt, DERBY1539V4statDropTriggerOnRevokeRequiredPrivilege.txt > > > A trigger tracks its privileges requirements using Derby's Dependency Manager. If any one of those required privileges are revoked, the trigger 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