Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 27350 invoked from network); 10 Mar 2009 15:39:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Mar 2009 15:39:14 -0000 Received: (qmail 28881 invoked by uid 500); 10 Mar 2009 15:39:13 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 28838 invoked by uid 500); 10 Mar 2009 15:39:13 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 28829 invoked by uid 99); 10 Mar 2009 15:39:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Mar 2009 08:39:13 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Mar 2009 15:39:11 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D18CC234C003 for ; Tue, 10 Mar 2009 08:38:50 -0700 (PDT) Message-ID: <1805881225.1236699530843.JavaMail.jira@brutus> Date: Tue, 10 Mar 2009 08:38:50 -0700 (PDT) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2487) Enhance Derby with EXPLAIN Functionality In-Reply-To: <11016305.1174903532140.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680511#action_12680511 ] Rick Hillegas commented on DERBY-2487: -------------------------------------- Hi Bryan, I would be tempted to not worry much about synonyms and views. It's true, those edge-cases could arise but I think the probability is very low, the negative consequences are slight, and the workaround is easy (turn off plan-gathering until you understand what's broken). I don't think you have to worry about schema mismatch for this first increment--the person who wants to change the shape of these tables can work through those issues later on. > Enhance Derby with EXPLAIN Functionality > ---------------------------------------- > > Key: DERBY-2487 > URL: https://issues.apache.org/jira/browse/DERBY-2487 > Project: Derby > Issue Type: New Feature > Components: SQL > Affects Versions: 10.2.2.0 > Reporter: Felix Beyer > Assignee: Bryan Pendleton > Priority: Minor > Attachments: Derby physical XPLAIN schema.png, incorporateTrunkChanges.diff, removeSourceDepth.diff, RSProtocolNew.pdf, rts.xls, small logical xplain schema.pdf, startRegressionTest.diff, startRegressionTest.diff, startUpgradeTests.diff, updateRegressionTests.diff, updateRegressionTests.diff, usage.txt, xplain_patch_v1.txt, xplainClasses.pdf > > > This enhancement extends Derby with EXPLAIN functions. Users want to have more feedback than they`re getting with the current RuntimeStatistics facility. This extension is based on the RuntimeStatistics/ResultSetStatistics functions / classes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.