Hi,
After working on much of the ground work for revoke, I have finally come to implement the revoke privilege such that only the objects that depend on the specific permission type being revoked should drop themselves.
I thought I could do that by having dependency manager sendspecific action
BTW, I think the issue is really with just triggers.
Views can only depend on select privileges, since we don't allow DML through views. So,when a ViewDescriptor gets an action anything other than REVOKE_SELECT_PRIVILEGE from dependency manager, it can simply ignore them. And for a
Hi,
I wondered if anyone got a chance to go over my earlier mail and if they think of an alternative way to solve the problem than the one suggested by me. If I don't hear anything in a day or so, then I will go ahead and changeSYSTABLEPERMS to look like SYSCOlPERMS. After that change, I will be
Mamta Satoor wrote:
[example snipped]
revoke select on t1 from user2
-- at this point, only view user2.v1 should get dropped because it depends
on the SELECTPRIV on t1. But dependency manager has no way to know that
user2.v1 needs only SELECTPRIV and hence only object affected by this
That is on my todo list to figure out when I do the revoke privilege implementation. But I am thinking that when a revoke privilege is processed, before dropping the dependent objects, a check will be made to see if some other privilege can replace the privilege being revoked and if so, then make
Have you considered using PROVIDERFINDER that is part of dependency system? TableDescriptor, for example, stores column list that a view depends on using ColumnsInTable finder. A similar mechanism might work for TablePermDescriptor.
SatheeshOn 7/10/06, Mamta Satoor [EMAIL PROTECTED] wrote:
Hi,
I
Mamta Satoor wrote:
That is on my todo list to figure out when I do the revoke privilege
implementation. But I am thinking that when a revoke privilege is
processed,
before dropping the dependent objects, a check will be made to see if some
other privilege can replace the privilege being
After reading you mail, it seems like with revoke, I can send specific action type to dependent objects ie say REVOKE_SELECT_PRIVILEGE / REVOKE_UPDATE_PRIVILEGE/ REVOKE_REFERENCES_PRIVILEGE etc rather than generic REVOKE_PRIVILEGE and that way dependent objects can see if they depend on that
Hi,
I recently submitted a patch (http://www.nabble.com/-PATCH-DERBY-1330-Collect-privilege-requirements-for-views-tf1858264.html#a5075008
)that tracks a view's(view descriptor)dependency on different privileges (PermissionsDescriptor)using the dependency manager which in turn saves these
