Apache Derby Database Engine and Embedded JDBC Driver 10.17.1.0 · org.apache.derby.iapi.sql.compile.OptimizerFactory

Modifier and Type	Field and Description
public static final String	MODULE Module name for the monitor's module locating system.

Method Summary

Modifier and Type	Method and Description
public boolean	Returns: `true` means do join order optimization, `false` means don't do it. doJoinOrderOptimization() Tell whether to do join order optimization.
public CostEstimate	getCostEstimate() Return a new CostEstimate.
public int	Returns: maxMemoryPerTable value getMaxMemoryPerTable() Return the maxMemoryPerTable setting, this is used in optimizer, as well as subquery materialization at run time.
public Optimizer	getOptimizer(OptimizableList The list of Optimizables to optimize. optimizableList, OptimizablePredicateList The list of unassigned OptimizablePredicates. predicateList, DataDictionary The DataDictionary to use. dDictionary, RequiredRowOrdering The required ordering of the rows to come out of the optimized result set requiredRowOrdering, int The number of tables in the current query numTablesInQuery, OptimizerPlan (Optional) A complete plan specified by optimizer overrides. Must have been bound already. overridingPlan, LanguageConnectionContext The LanguageConnectionContext RESOLVE - We probably want to pass a subquery list, once we define a new interface for them, so that the Optimizer can out where to attach the subqueries. lcc) Only one optimizer level should exist in the database, however, the connection may have multiple instances of that optimizer at a given time.
public boolean	Returns: Whether or not the optimizer associated with this factory supports optimizer trace. supportsOptimizerTrace() Return whether or not the optimizer associated with this factory supports optimizer trace.

MODULE	back to summary
public static final String MODULE Module name for the monitor's module locating system.

Method Detail

doJoinOrderOptimization back to summary

doJoinOrderOptimization	back to summary
public boolean doJoinOrderOptimization() Tell whether to do join order optimization. Returns:boolean `true` means do join order optimization, `false` means don't do it.

public boolean doJoinOrderOptimization()

Tell whether to do join order optimization.

Returns:boolean: true means do join order optimization, false means don't do it.

getCostEstimate	back to summary
public CostEstimate getCostEstimate() Return a new CostEstimate.

getMaxMemoryPerTable	back to summary
public int getMaxMemoryPerTable() Return the maxMemoryPerTable setting, this is used in optimizer, as well as subquery materialization at run time. Returns:int maxMemoryPerTable value

getMaxMemoryPerTable

back to summary

public int getMaxMemoryPerTable()

Return the maxMemoryPerTable setting, this is used in optimizer, as well as subquery materialization at run time.

Returns:int: maxMemoryPerTable value

getOptimizer	back to summary
public Optimizer getOptimizer(OptimizableList optimizableList, OptimizablePredicateList predicateList, DataDictionary dDictionary, RequiredRowOrdering requiredRowOrdering, int numTablesInQuery, OptimizerPlan overridingPlan, LanguageConnectionContext lcc) throws StandardException Only one optimizer level should exist in the database, however, the connection may have multiple instances of that optimizer at a given time. Parameters optimizableList:OptimizableList The list of Optimizables to optimize. predicateList:OptimizablePredicateList The list of unassigned OptimizablePredicates. dDictionary:DataDictionary The DataDictionary to use. requiredRowOrdering:RequiredRowOrdering The required ordering of the rows to come out of the optimized result set numTablesInQuery:int The number of tables in the current query overridingPlan:OptimizerPlan (Optional) A complete plan specified by optimizer overrides. Must have been bound already. lcc:LanguageConnectionContext The LanguageConnectionContext RESOLVE - We probably want to pass a subquery list, once we define a new interface for them, so that the Optimizer can out where to attach the subqueries. Exceptions StandardException: Thrown on error

getOptimizer

back to summary

public Optimizer getOptimizer(OptimizableList optimizableList, OptimizablePredicateList predicateList, DataDictionary dDictionary, RequiredRowOrdering requiredRowOrdering, int numTablesInQuery, OptimizerPlan overridingPlan, LanguageConnectionContext lcc) throws StandardException

Only one optimizer level should exist in the database, however, the connection may have multiple instances of that optimizer at a given time.

Parameters

optimizableList:OptimizableList: The list of Optimizables to optimize.
predicateList:OptimizablePredicateList: The list of unassigned OptimizablePredicates.
dDictionary:DataDictionary: The DataDictionary to use.
requiredRowOrdering:RequiredRowOrdering: The required ordering of the rows to come out of the optimized result set
numTablesInQuery:int: The number of tables in the current query
overridingPlan:OptimizerPlan: (Optional) A complete plan specified by optimizer overrides. Must have been bound already.
lcc:LanguageConnectionContext: The LanguageConnectionContext RESOLVE - We probably want to pass a subquery list, once we define a new interface for them, so that the Optimizer can out where to attach the subqueries.

Exceptions

StandardException:: Thrown on error

supportsOptimizerTrace	back to summary
public boolean supportsOptimizerTrace() Return whether or not the optimizer associated with this factory supports optimizer trace. Returns:boolean Whether or not the optimizer associated with this factory supports optimizer trace.

supportsOptimizerTrace

back to summary

public boolean supportsOptimizerTrace()

Return whether or not the optimizer associated with this factory supports optimizer trace.

Returns:boolean: Whether or not the optimizer associated with this factory supports optimizer trace.

public Interface OptimizerFactory

Field Summary

Method Summary

Field Detail

Method Detail