db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4272) SQL Authorization Support for dblook
Date Sat, 22 Aug 2009 17:04:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746481#action_12746481

Dag H. Wanvik commented on DERBY-4272:

> I think it is required to maintain some backward compatibility? (as
> discussed on the mailing list). It was mentioned that without the
> CONNECT statements commented out, we cannot directly send the output
> of dblook to ij using pipes.

Yes backward compatibility it is a concern, but for the case when
authentication[1] and SQLAuthorization[2] is enabled, dblook hasn't
really been working at all till now, so I think we are free to choose
what to do for that case.

Without authentication and SQLAuthorization enabled, there is really
no point in creating objects from more than one session anyway; the db object's schema
is all that matters, since all connected users can access all objects.


[1] derby.connection.requireAuthentication=true

[2] derby.database.SQLAuthorization=true

> 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-u1.patch, DERBY-4272-u2.patch, DERBY-4272-u3.patch,
DERBY-4272-u4.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
> 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.

View raw message