db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@apache.org>
Subject Re: Grant/revoke dual mode - is derby.database.sqlAuthorization needed?
Date Thu, 27 Jul 2006 18:37:52 GMT
Satheesh Bandaram wrote:

> Daniel John Debrunner wrote:
> 
> 
>>Do we really need such a property to be part of the public api, it just
>>makes Derby that little bit harder to use.
>>
>>Why not base the switching of the mode on the first successful execution
>>of a GRANT statement?
>>
>>I also dislike the two modes, and am stil looking at ways to avoid it.
>> 
>>
> 
> It is a worthy cause... if you can find an appropriate way to achieve
> this. We did talk about switching the mode during first execution of a
> GRANT statement and was rejected before. See this thread and several others:
> 
> http://www.nabble.com/Re%3A-Grant-and-Revoke%2C-Part-I-...-DERBY-464...-p2410538.html
> 
> This is because of several reasons...

>    2. Can any user switch the mode  triggered internally or only
>       database owner's GRANT statement would switch the mode? How do you
>       account for "accidental" switching of the mode when their real
>       "intent" is not to switch? Derby doesn't support switching mode
>       from SQL authorization back to Derby authorization mode.

According to the functional spec in DERBY-464, any user can perform the
switch to GRANT/REVOKE mode.

Probably if a GRANT statement triggered the switch it should be only by
the database owner.

Dan.


Mime
View raw message