Hi,
Based on functional specification attached to DERBY-1330, I am working on having REVOKE REFERENCES privilege drop all the foreign key constraints dependent on that privilege.
I thought, this would involve going through SYSTABLEPERMS and SYSCOLPERMS in execute phase of of REVOKE statement t
Hi,
Did anyone get a chance to go through this mail and see if I am going the right track for solving the problem?
thanks,
Mamta
On 7/8/06, Mamta Satoor <[EMAIL PROTECTED]> wrote:
Hi,
Based on functional specification attached to DERBY-1330, I am working on having REVOKE REFERENCES privile
Hi,
I spent some time prototyping revoke privilege for foreign key constraint based on my proposal earlier in this thread.
I added following code to ConstraintDescriptor.makeInvalid
if (action == DependencyManager.REVOKE_PRIVILEGE) { PreparedStatement ps = lcc.prepareInternalStatement("al
Mamta Satoor wrote:
> Hi,
>
> I spent some time prototyping revoke privilege for foreign key constraint
> based on my proposal earlier in this thread.
> I added following code to ConstraintDescriptor.makeInvalid
>
> if (action == DependencyManager.REVOKE_PRIVILEGE)
> {
> PreparedStatement ps
Yes, that is what I had originally tried, which is to have the ConstraintDescriptor.makeInvalid call following when it receives REVOKE_PRIVILEGE action
getDataDictionary().dropConstraintDescriptor(getTableDescriptor(), this, lcc.getTransactionExecute());
But looks like that is not sufficient to h
[ Possible re-send of this message; I've been having email problems, sorry. ]
> I looked through alter table constant action to see what happens
> when a user issues a drop constraint foreignkeyname and it seems
> like there is lot more involved then simply calling the dat
Bryan Pendleton wrote:
> [ Possible re-send of this message; I've been having email problems,
> sorry. ]
>
>> I looked through alter table constant action to see what happens
>> when a user issues a drop constraint foreignkeyname and it seems
>> like there is lot more invol
Hi,
While working on revoke privilege, I realized that when a table/view/routine is dropped, we do not drop the privileges that were defined on those objects. This is a known issue and Satheesh already has plans of working on it. But, out of curiosity, I was looking at
DropTableConstantAction.ex
