db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1522) Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
Date Thu, 10 Aug 2006 22:40:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12427361 ] 
            
Deepa Remesh commented on DERBY-1522:
-------------------------------------

I had briefly looked at this task as I was working on DERBY-1521. I think we can cover the
testing suggested by doing the following:

1) Create a database without setting derby.database.sqlAuthorization system property.
2) Test that grant/revoke statements are not supported
3) Set derby.database.sqlAuthorization (as a database property) to true. Shutdown and reconnect
to database.
4) Test grant/revoke works by running lang/grantRevokeDDL.sql. This test seems to cover all
the scenarios suggested.
5) Set derby.database.sqlAuthorization (as a database property) to false. Shutdown and reconnect
to database.
6) Test that grant/revoke still works.

To me. only step 4 (running the existing test) seems to be a bit involved. Dan has suggested
few options for this in DERBY-1521. Just posting this in case someone is planning to get to
it soon.


> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs
to be tested
> ----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1522
>                 URL: http://issues.apache.org/jira/browse/DERBY-1522
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.2.0.0
>            Reporter: Mamta A. Satoor
>             Fix For: 10.2.0.0
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization
to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch
like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the
right component.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message