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-3868) dblook generates SET SCHEMA null and fails to produce correct schema for view
Date Thu, 04 Sep 2008 17:03:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628385#action_12628385
] 

Dag H. Wanvik commented on DERBY-3868:
--------------------------------------

What is the intention with the dblook output anyway? Should it
generate a runnable script or not?  If not, why generate the SET
SCHEMA statements? In the output above, the table is generated with an
explicit schema name, but the view is not.

The docs don't mention it, but dblook will also generate GRANT
privileges statements if SQL authorization is enabled, but if the
example in the repro is run with SQL authorization enabled, the GRANT
SELECT will be generated *after* the CREATE VIEW statement (see
uploaded reproscript-auth.sh). 

Also, since no connect statements are generated, all created objects
would be owed by the same user if one attempted to run the output as
an ij script, so it seems the output from dblook is far from from a
runnable script.

I guess that's ok if the docs make that clear, it's just that the SET
SCHEMA statements give the impression of a runnable script. The dblook
docs don't seem to discuss SQL authorization, though. Does anyone know
what is the current state of dblook with respect to these issues?



> dblook generates SET SCHEMA null and fails to produce correct schema for view
> -----------------------------------------------------------------------------
>
>                 Key: DERBY-3868
>                 URL: https://issues.apache.org/jira/browse/DERBY-3868
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Dag H. Wanvik
>         Attachments: reproscript.sh
>
>
> Scenario: One user creates a table, another user creates a view of the first user's table.
> dblook output show below (reproscript.sh uploaded).
> > -- Timestamp: 2008-09-04 18:43:33.186
> > -- Source database is: wombat
> > -- Connection URL is: jdbc:derby:wombat;user=dag;password=wanvik
> > -- appendLogs: false
> > 
> > -- ----------------------------------------------
> > -- DDL Statements for schemas
> > -- ----------------------------------------------
> > 
> > CREATE SCHEMA "DAG";
> > 
> > CREATE SCHEMA "KNUT";
> > 
> > -- ----------------------------------------------
> > -- DDL Statements for tables
> > -- ----------------------------------------------
> > 
> > CREATE TABLE "DAG"."T" ("I" INTEGER);
> > 
> > -- ----------------------------------------------
> > -- DDL Statements for views
> > -- ----------------------------------------------
> > 
> > SET SCHEMA null;
> > create view v as select * from dag.t;
> > 
> > -- Reverting back to default schema 'APP'
> > SET SCHEMA "APP";
> The SET SCHEMA null is illegal and the view "v" is not correctly
> qualified with its schema name ("KNUT"). 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message