[
https://issues.apache.org/jira/browse/DERBY-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720521#action_12720521
]
Hiranya Jayathilaka commented on DERBY-4272:
--------------------------------------------
My plan was to make the DiGraph class a general data structure which can be
used to store any kind of data through generics. That way we could have used it
to store the dependency graph as well as the role dependency graph (and any
other directed graph we'll ever need). Anyway if generics cannot be used I'll
make this class specific to the DBPersistentObject type. That will not alter
the existing functionality but for the role dependency graph we'll have to
write another data structure in the near future.
I'll send in a new patch soon.
> 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
> Attachments: DERBY-4272-changes-u1.txt, DERBY-4272-u1.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.
