Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <469FF91F.3090909@amberpoint.com>
Date: Thu, 19 Jul 2007 16:51:59 -0700
From: Bryan Pendleton <bpendleton@amberpoint.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: predicates missing from the optimized tree dump
References: <5ba791c80707191419j6f31010awd4dbb6363ff695f@mail.gmail.com>
In-Reply-To: <5ba791c80707191419j6f31010awd4dbb6363ff695f@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

> I want to understand if this was intentionally left this way so that the 
> output does not become too long or is this something that is missing(I 
> would assume atleast the predicates to be dumped out).

In a couple cases I've encountered what I felt were missing overrides
of printSubNodes myself, so my instinct is that this was an oversight,
not intentional, and would be useful functionality to add.

In general, we've been pretty liberal with the verbosity of the
tree-dumping, as it tends to be only used by the developers.

There have been periodic discussions about improving this section
of the system. The suggestion that has gathered a lot of support is
to capture the internal query plan dump output into XML format and
store it into special tables directly in the database itself, where
we could then use Derby's own XML features to process it effectively.

However, such a feature has not yet been implemented.

thanks,

bryan