[ 
http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12424703 ] 
            
Mamta A. Satoor commented on DERBY-1522:
----------------------------------------

Deepa, you are right about testing the switch for both of following cases
1)As part of pre-10.2 db upgrade
2)A database created in 10.2  w/o SQL Standard Authorization gets switched to 
SQL Standard Authorization

I haven't given much thought to what kind of testing is involved. One thing 
that comes to my mind though is after the upgrade, all the existing schemas and 
objects in them should be owned by the dba and any other users will need to 
have permissions granted to them by the dba. Also, right after the upgrade, 
there should be nothing in the permissions related system tables because dba 
owns everything and no permissions has been granted to anyone yet. Similarly, 
the dependency manager should not have any permission related dependencies 
because dba does not need any permissions. Currently, dependency manager uses 
SYSDEPENDS table to keep track of permissions required for various objects. So, 
a check of SYSDEPENDS for permission dependencies will be a good idea in the 
tests right after the upgrade.

If anyone thinks of any other tests that we should be writing, please add them 
to this Jira entry.

> 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: JDBC
>    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

        

Reply via email to