Hiranya Jayathilaka wrote:
One more question.
We initially intended to use a dependency graph to capture the
dependencies among different roles. But looking at the SYSROLES table
and the existing role handling code I'm not sure whether we really
need that. Isn't creating all the roles in one swoop and then
performing all the grants (also recorded in SYSROLES table)
sufficient? I can't seem to realize how this will break any
inter-dependencies among roles.
Hi Hiranya,
I think that the creating of roles and granting of roles to roles can
all be done at once. It is the granting of privileges to the roles that
has to be interleaved with the creation of other objects. The issues are
discussed on this jira: https://issues.apache.org/jira/browse/DERBY-3877
Hope this helps,
-Rick
Thanks,
Hiranya
On Sun, Jul 19, 2009 at 4:21 PM, Hiranya Jayathilaka
<[email protected] <mailto:[email protected]>> wrote:
Hi Folks,
I'm now into implementing roles support for the improved dblook
implementation. Current dblook implementation simply creates all
the roles and does the necessary role grants, before start
creating other persistent objects. I guess I could do the same
reusing most if not all of the existing code. However I think in
the new implementation we need to capture the dependency a
persistent object may have on a role. Can somebody please let me
know where these dependencies are recorded? Is it in the SYSDEPENDS?
Secondly we need to set the necessary role before going on to
creating any object. What is the SQL for this? Is it something
like SET ROLE {ROLENAME}? Also I guess I might have to 'unset'
roles after creating an object? Is that correct?
Thanks,
Hiranya Jayathilaka
--
Hiranya Jayathilaka
Software Engineer;
WSO2 Inc.; http://wso2.org
E-mail: [email protected] <mailto:[email protected]>; Mobile: +94 77
633 3491
Blog: http://techfeast-hiranya.blogspot.com
