[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12425289 ] Mamta A. Satoor commented on DERBY-1522: ----------------------------------------
Deepa, to be more precise, in my statement "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." , the *dba* is the user who is attempting the upgrade. So, the correct behavior should be what DERBY-1544 is proposing to do. I think DERBY-1544 should go into 10.2 but I am not sure if anyone is looking into it. > 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
