db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4645) Dropping one of the XPLAIN system tables while XPLAIN is enabled results into an exception. Trying it again succeeds.
Date Mon, 10 May 2010 14:32:17 GMT

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

Bryan Pendleton commented on DERBY-4645:
----------------------------------------

Thanks Mamta.

I'm not really certain which behavior is better; the first time or the second time.

It is definitely confusing to have two different behaviors, though.

What was the final outcome after the experiment? Was the TIMINGS table
present, or had it been successfully dropped?


> Dropping one of the XPLAIN system tables while XPLAIN is enabled results into an exception.
Trying it again succeeds.
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4645
>                 URL: https://issues.apache.org/jira/browse/DERBY-4645
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.6.1.0
>            Reporter: Mamta A. Satoor
>            Priority: Minor
>         Attachments: derby.log
>
>
> Ran into an exception when I tried dropping system table SYSXPLAIN_STATEMENT_TIMINGS
after enabling XPLAIN logging using CALL SYSCS_UTIL.SYSCS_SET_XPLAIN_SCHEMA('XPLAINSCHEMA');
The second attempt at dropping the table succeeds
> eg ij script
> $ java org.apache.derby.tools.ij
> ij version 10.6
> ij> connect 'jdbc:derby:c:/dellater/buddytest10_6_1;create=true';
> ij> CALL SYSCS_UTIL.SYSCS_SET_RUNTIMESTATISTICS(1);
> 0 rows inserted/updated/deleted
> ij> CALL SYSCS_UTIL.SYSCS_SET_STATISTICS_TIMING(1);
> 0 rows inserted/updated/deleted
> ij> CALL SYSCS_UTIL.SYSCS_SET_XPLAIN_SCHEMA('XPLAINSCHEMA');
> 0 rows inserted/updated/deleted
> ij> values syscs_util.syscs_get_xplain_schema();
> 1
> --------------------------------------------------------------------------------
> XPLAINSCHEMA
> 1 row selected
> ij> set schema XPLAINSCHEMA;
> 0 rows inserted/updated/deleted
> ij> drop table SYSXPLAIN_STATEMENT_TIMINGS;
> java.sql.SQLSyntaxErrorException: Table/View 'XPLAINSCHEMA.SYSXPLAIN_STATEMENT_TIMINGS'
does not exist.
> ij> drop table SYSXPLAIN_STATEMENT_TIMINGS;
> 0 rows inserted/updated/deleted
> I wonder if this is happening because we are trying to write into SYSXPLAIN_STATEMENT_TIMINGS
as part of the XPLAIN functionality when first drop table for SYSXPLAIN_STATEMENT_TIMINGS
is issued. 

-- 
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