db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satheesh Bandaram <sathe...@Sourcery.Org>
Subject Re: [jira] Commented: (DERBY-464) Enhance Derby by adding grant/revoke support. Grant/Revoke provide finner level of privileges than currently provided by Derby that is especially useful in network configurations.
Date Fri, 17 Feb 2006 07:15:54 GMT
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
OK... I will see if check() method interface can be changed..<br>
Daniel John Debrunner wrote:<br>
<blockquote cite="mid43F5036E.4020904@apache.org" type="cite">
  <pre wrap="">Satheesh Bandaram (JIRA) wrote:

  <blockquote type="cite">
    <pre wrap="">All implement check() interface that is used to invoke permission checking
for that access descriptor. Access descriptors already know what they need to check for and
are passed current user authorizationId.
  <pre wrap=""><!---->
Since g/r is a language issue, it seems like the check() method should
take the LCC and not the transaction controller. Then the authorization
id would be available in the LCC and not have the potential to be
different. Or can it be different, again comments needed here.

  <blockquote type="cite">
    <pre wrap="">The equals() method is used to check if an access descriptor is already
created for the specific access. For example, a query may have multiple references to same
table. No need to create multiple access descriptors for the same table for the same kind
of access. This becomes more important as each and every column referenced may try to add
an access descriptor for the table in question.

I will add these details to the design part of the spec.
  <pre wrap=""><!---->
And to the java code, right?



View raw message