[jira] [Commented] (TRAFODION-312) LP Bug: 1323922 - Regular table is not dropped when a volatile table is present

["Roberta Marton (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TRAFODION-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706971#comment-14706971 ] 

Roberta Marton commented on TRAFODION-312:
------------------------------------------

Problem fixed 6/2014

QA verified.

> LP Bug: 1323922 - Regular table is not dropped when a volatile table is present
> -------------------------------------------------------------------------------
>
>                 Key: TRAFODION-312
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-312
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: sql-exe
>            Reporter: Weishiun Tsai
>            Assignee: Roberta Marton
>            Priority: Critical
>
> The following short script demonstrates this strange behavior.  When a volatile table was created, dropping a regular table (with a different name) did not take effect.  Even though the drop statement said that the operation was complete, but 'get tables' afterwards still showed the table.
> With the same script, if the 'create volatile table' statement was commented out, the table was dropped just fine.
> This is seen on the datalake v40963 build installed on a workstation.
> -------------------------------------------
> Here is the script to reproduce this problem:
> set schema mytest10;
> get tables;
> create volatile table ta1 (a int default 12);
> get tables;
> create table tb1 (a int, b int);
> drop table tb1;
> get tables;
> -------------------------------------------
> Here is the execution output.  The last 'get tables' still showed the table even though the previous statement already dropped it.
> -bash-4.1$ sqlci
> Trafodion Conversational Interface 0.7.0
> (c) Copyright 2014 Hewlett-Packard Development Company, LP.
> >>obey mytest.sql;
> >>set schema mytest10;
> --- SQL operation complete.
> >>get tables;
> --- SQL operation complete.
> >>create volatile table ta1 (a int default 12);
> --- SQL operation complete.
> >>get tables;
> --- SQL operation complete.
> >>create table tb1 (a int, b int);
> --- SQL operation complete.
> >>drop table tb1;
> --- SQL operation complete.
> >>get tables;
> Tables in Schema TRAFODION.MYTEST10
> ===================================
> TB1
> --- SQL operation complete.
> -------------------------------------------
> Here is the execution output to show that if the volatile table creation is commented out, the table is dropped just fine.
> -bash-4.1$ sqlci
> Trafodion Conversational Interface 0.7.0
> (c) Copyright 2014 Hewlett-Packard Development Company, LP.
> >>obey mytest.sql;
> >>set schema mytest20;
> --- SQL operation complete.
> >>get tables;
> --- SQL operation complete.
> >>-- create volatile table ta1 (a int default 12);
> >>-- get tables;
> >>create table tb1 (a int, b int);
> --- SQL operation complete.
> >>drop table tb1;
> --- SQL operation complete.
> >>get tables;
> --- SQL operation complete.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)