[
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-u5.txt
DERBY-4272-u5.patch
* Removed Java 5 annotations
* Made some minor changes to the code to get it compiled on JDK 1.4 (eg: using
Integer objects when dealing with maps instead of int)
* APP schema is now ignored when creating schemas
* SET ROLE NONE statements are printed correctly
* The DBO will create a connection before creating the roles
* Minor changes to DDL generation logic (formatting changes)
To get the DBO username I used conn.getMetaData().getUserName(). But I think
this will work properly only if we start dblook with a connection belonging to
DBO. Is that ok? If not what is the right way to find the DBO username?
On a different note do we really need to create a connection (in the generated
script) as DBO before creating roles? In order to run the generated script we
need to create a connection anyway.
The test case is coming along nicely. I may have some question on that. Will
start a mail thread regarding them 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
> 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.
