You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org> on 2009/12/15 17:12:18 UTC
[jira] Updated: (DERBY-4272) SQL Authorization Support for dblook
[ 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-u6.txt
DERBY-4272-u6.patch
Uploading the patch for all my workings so far. Includes:
* Complete source code including some of the recent fixes I have done to the code for the bugs discovered during testing
* Partially completed test cases and related resources
> 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-changes-u6.txt, DERBY-4272-u1.patch, DERBY-4272-u2.patch, DERBY-4272-u3.patch, DERBY-4272-u4.patch, DERBY-4272-u5.patch, DERBY-4272-u6.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.