[
https://issues.apache.org/jira/browse/DERBY-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiranya Jayathilaka updated DERBY-4272:
---------------------------------------
Attachment: DERBY-4272-changes-u4.txt
DERBY-4272-u4.patch
Attaching feature complete patch. Changes made since the last patch:
* Implemented support for creating and granting roles
* Implemented support for setting the necessary roles before constructing each
object
* Implemented support for synonyms
* Implemented support for handling view permission grants
* Changed the DDL generation logic foe views so that it would use full
qualified view names in the CREATE statements - With this we no longer need to
explicitly set the schema before creating a view
* Added comments and javadocs
* Minor code refactoring and cleanup work
> SQL Authorization Support for dblook
> ------------------------------------
>
> Key: DERBY-4272
> URL: https://issues.apache.org/jira/browse/DERBY-4272
> Project: Derby
> Issue Type: Improvement
> Components: Tools
> Environment: Any
> Reporter: Hiranya Jayathilaka
> Assignee: Hiranya Jayathilaka
> Attachments: DERBY-4272-changes-u1.txt, DERBY-4272-changes-u2.txt,
> DERBY-4272-changes-u3.txt, DERBY-4272-changes-u4.txt, DERBY-4272-u1.patch,
> DERBY-4272-u2.patch, DERBY-4272-u3.patch, DERBY-4272-u4.patch
>
>
> Currently dblook suffers from two major shortcomings.
> 1. dblook doesn't take the object dependencies into consideration when
> generating DDL scripts
> 2. dblook doesn't have any support for SQL authorization
> I intend to fix these two issues and improve dblook so that the DDL scripts
> generated by dblook can be executed without errors under all conditions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
