[
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-u3.txt
DERBY-4272-u3.patch
* Implemented dependency graph based DDL generation for jar files, views,
triggers and indexes
* Minor code refactoring and cleanup work based on the feedback from the
community
* Implemented a switch to change the behavior of SQL CONNECT statement
generation (by default such statements will be commented out - use connectStmt
argument to change this behavior)
With this patch we can generate a DDL for a database without roles support. My
next patch will focus on getting in roles support based on the dependency graph.
As always I'd appreciate any feedback on this patch :)
> 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-u1.patch, DERBY-4272-u2.patch,
> DERBY-4272-u3.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.
