[ http://issues.apache.org/jira/browse/DERBY-1544?page=all ]
Deepa Remesh updated DERBY-1544:
--------------------------------
Attachment: d1544-patch1-v1.diff
d1544-patch1-v1.status
Attaching a patch 'd1544-patch1-v1.diff' which is same as the draft patch + a
test. This patch solves the first part of this sub-task.
This patch modifies only DataDictionaryImpl.updateSchemaAuth method which is
used only in the upgrade path. Hence I have only run the upgrade test with this
patch. I also verified that the newly added check in the test fails without the
patch and passes with it.
Please review/commit this patch. Thanks.
> 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
> Assigned To: Deepa Remesh
> Fix For: 10.2.0.0
>
> Attachments: d1544-patch1-draft.diff, d1544-patch1-v1.diff,
> d1544-patch1-v1.status
>
>
> 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
