[
https://issues.apache.org/jira/browse/DERBY-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiranya Jayathilaka updated DERBY-4272:
---------------------------------------
Attachment: new.sql
old.sql
Attaching two DDL files generated by using the existing dblook implementation
(old.sql) and improved dblook implementation (new.sql) for some early feedback.
Both scripts are against the same database.
Note how the new dblook implementation switches between multiple database
connections (CONNECT statements are printed as comments - this behavior
isconfigurable through a command line argument) when constructing objects.
Also note how it sets the roles before constructing each object. The
dependencies among objects are also preserved. Permission grants take place
interleaved with object creation.
The database used for DDL generation does not have too many objects. Will
provide some more sample scripts for a database having a large number of
objects.
> 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, new.sql,
> old.sql
>
>
> 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.
