Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <43F5036E.4020904@apache.org>
Date: Thu, 16 Feb 2006 14:57:50 -0800
From: Daniel John Debrunner <djd@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.3) Gecko/20040910
MIME-Version: 1.0
To: derby-dev@db.apache.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.
References: <1220360668.1140129960696.JavaMail.jira@ajax.apache.org>
In-Reply-To: <1220360668.1140129960696.JavaMail.jira@ajax.apache.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Satheesh Bandaram (JIRA) wrote:


> 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.

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.

> 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.

And to the java code, right?

Dan.