BTW, I have made a JIRA entry for this. The number is Derby-837. I have marked it as a new feature. Another option could have been improvement. Hopefully new feature is the right criteria, even if this will be used only by developers and not a documented feature. Also, for the Component, I was thinking of marking it as Performance but it didn't sound right. So, for now, I have left it as Unknown.
Mamta
On 1/19/06, Jeffrey Lichtman <[EMAIL PROTECTED]> wrote:
>I am curious about your statement "This tracing feature is intended
>for developers who are debugging optimizer problems. I don't believe
>it should ever be exposed as a supported feature....".
As soon as you expose a feature you have to support it, which means
documentation, compatibility issues, user handholding, etc. Since the
optimizer trace output doesn't mean anything to someone who doesn't
know the guts of the optimizer, I would say we're better off just
letting developers know it exists.
- Jeff Lichtman
[EMAIL PROTECTED]
Check out Swazoo Koolak's Web Jukebox at
http://swazoo.com/
