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.
