[jira] Commented: (DERBY-1304) DROP view does not always completely remove view

["Satheesh Bandaram (JIRA)" <de...@db.apache.org>]

    [ http://issues.apache.org/jira/browse/DERBY-1304?page=comments#action_12378502 ] 

Satheesh Bandaram commented on DERBY-1304:
------------------------------------------

I believe this problem would showup only when target schema of the view doesn't match current schema. In the example above, current schema is probably NOT test_schema, where the view is being created in. That is also why the problem doesn't show when setting current schema to TEST_SCHEMA as suggested by Rajesh. If this is the case, I would suggest changing the description to indicate that the problem shows up only under this condition.

Also, the Component should be SQL. Store is probably not at fault here.


> DROP view does not always completely remove view
> ------------------------------------------------
>
>          Key: DERBY-1304
>          URL: http://issues.apache.org/jira/browse/DERBY-1304
>      Project: Derby
>         Type: Bug

>   Components: Store
>     Versions: 10.1.2.1
>  Environment: Windows XP
>     Reporter: Piet Blok

>
> Execute the following scenario:
> Create a schema
> Create a table
> Create a view
> Drop the view
> Drop the table
> Drop the schema
> The first time this sequence executes OK, However, executing the same sequence again fails on the drop view:
> ERROR X0X05: Table 'view' does not exist.
> When I leave out the create and drop of a view, all goes well, so it seems 
> to have something to do with the view.
> I encountered the problem first using org.apache.derby.jdbc.ClientConnectionPoolDataSource, but later I found that the problem is reproducable with a simple ij script as follows:
> -- *******************************************************
> -- Setup connection
> -- *******************************************************
> connect 'jdbc:derby://localhost/TestData;create=true;';
> -- *******************************************************
> -- The first time
> -- *******************************************************
> CREATE SCHEMA TEST_SCHEMA;
> CREATE TABLE TEST_SCHEMA.T1 (TABLE_COLUMN LONG VARCHAR);
> CREATE VIEW TEST_SCHEMA.V1 AS SELECT TABLE_COLUMN AS VIEW_COLUMN FROM 
> TEST_SCHEMA.T1;
> DROP VIEW TEST_SCHEMA.V1;
> DROP TABLE TEST_SCHEMA.T1;
> DROP SCHEMA TEST_SCHEMA RESTRICT;
> -- *******************************************************
> -- The second time
> -- *******************************************************
> CREATE SCHEMA TEST_SCHEMA;
> CREATE TABLE TEST_SCHEMA.T1 (TABLE_COLUMN LONG VARCHAR);
> CREATE VIEW TEST_SCHEMA.V1 AS SELECT TABLE_COLUMN AS VIEW_COLUMN FROM 
> TEST_SCHEMA.T1;
> DROP VIEW TEST_SCHEMA.V1; -- This statement fails
> DROP TABLE TEST_SCHEMA.T1;
> DROP SCHEMA TEST_SCHEMA RESTRICT;
> -- *******************************************************
> -- Cleanup
> -- *******************************************************
> disconnect;
> connect 'jdbc:derby://localhost/TestData;shutdown=true;';
> As an explanation why I would like to be able to create and then drop views: I am trying to interactively create my table setup. When I make mistakes I must drop wrongly defined tables or views.
> I encountered some other very strange behaviour that might be related to this issue (table not found when I just created it and wanted to create a second table with a foreign key referencing the first table), but which I am not yet able to reproduce in a consistent and simple way.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira