[ http://issues.apache.org/jira/browse/DERBY-1544?page=comments#action_12423717 ]
Satheesh Bandaram commented on DERBY-1544:
------------------------------------------
Changes to update database owner is already present in Derby upgrade process.... it seems
there is a defect that is either not committing this transaction during upgrade or starting
transaction wrongly. Stepping through the code sometime ago, noticed upgrade does invoke this
internal mechanism to update 'DBA' as the owner of system schemas to authorizationID of the
invoker of upgrade, but probably because of wrong internal transaction semantics, the change
doesn't seem to get committed.
For the second part of the sub-task, full upgrade needs to add 5 routine perm descriptors
that allow GRANTing of EXECUTE privilege to 5 system routines that by default have execute
access. This code needs to be added, much like code that adds 5 system routine permission
descriptors during a NEW database creation.
> Address remaining upgrade task(s) to complete full upgrade mechanism for GRANT/REVOKE,
specifically with changing database owner name from 'DBA' to authorizationId of user invoking
upgrade.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1544
> URL: http://issues.apache.org/jira/browse/DERBY-1544
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 10.2.0.0
> Environment: generic
> Reporter: Satheesh Bandaram
> Fix For: 10.2.0.0
>
>
> Upgrading a database from 10.1 to 10.2 should automatically change database owner, recorded
as owner of system schemas in sysschemas, from pseudo user 'DBA' to authorizationID of the
user attempting upgrade.
> Another upgrade change I am thinking about is to grant execute privilege to 5 system
routines that by default have execute privilege to public when a new database is created.
Five system routines, two compress routines and three statistics related routines are given
execute privilege to public when a new 10.2 database is created. This is not done when a 10.1
database is upgraded to 10.2 and probably good to include these privileges during database
upgrade.
>
--
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