[
https://issues.apache.org/jira/browse/DERBY-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746678#action_12746678
]
Dag H. Wanvik commented on DERBY-4272:
--------------------------------------
> BTW you can get the CONNECT statements printed as regular DDL
> statements (uncommented) by passing the -connectStmt argument to
> dblook.
Good! Does that make the SET CONNECTION statements uncommented as
well?
> 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-changes-u5.txt, DERBY-4272-u1.patch, DERBY-4272-u2.patch,
> DERBY-4272-u3.patch, DERBY-4272-u4.patch, DERBY-4272-u5.patch,
> dhw-sample-1.sql, 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.
