Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0, 10.6.2.1, 10.7.1.1
-
None
-
Normal
Description
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").
Attachments
Attachments
Issue Links
- is related to
-
DERBY-3954 dblook scripts cannot be relied on to recreate the permissions and schema objects of a database
- Open
- relates to
-
DERBY-3877 SQL roles: build support for dblook
- Closed