Re: VTI, Indexed Lookup and the Query Optimizer

[Jeffrey Lichtman]

Is this what you were referring to, Jeff?
 

derby.language.logQueryPlan

Thanks, but that's not it. logQueryPlan causes the final query plan to be written to derby.log. I was thinking of a trace function that creates a trail of all the decisions and calculations the optimizer makes in derby.log. It looks to me like this is currently disabled, but would be easy to enable. OptimizerImpl.java contains the following:

        //
Optimzer trace
        public
void trace(int traceFlag, int intParam1, int intParam2,
        
        
        
        
          double
doubleParam, Object objectParam1)
        {
        }

and OptimizerFactoryImpl.java contains:

        /**
         * @see
OptimizerFactory#supportsOptimizerTrace
         */
        public
boolean supportsOptimizerTrace()
        {
        
        return false;
        }

It looks like it should be pretty easy to turn tracing on.

                       -        Jeff Lichtman
                                [EMAIL PROTECTED]
                                Check out Swazoo Koolak's Web Jukebox at
                                http://swazoo.com/