Method should_use_statement_cache

src/optimization/statement_cache_optimizer.rs:204–235

Determine if a query should use statement caching based on pattern and hints

(&self, pattern: &QueryPattern, hints: &OptimizationHints)

    /// Determine if a query should use statement caching based on pattern and hints
    fn should_use_statement_cache(&self, pattern: &QueryPattern, hints: &OptimizationHints) -> bool {
        use crate::query::{QueryPattern, QueryComplexity};

        match pattern {
            // Always cache these high-value patterns
            QueryPattern::SimpleSelect |
            QueryPattern::SimpleInsert |
            QueryPattern::SimpleUpdate |
            QueryPattern::SimpleDelete |
            QueryPattern::BatchInsert |
            QueryPattern::CountQuery |
            QueryPattern::MaxMinQuery => true,

            // Cache if optimization hints suggest it's beneficial
            QueryPattern::GroupByAggregation |
            QueryPattern::OrderByLimit |
            QueryPattern::JoinWithWhere |
            QueryPattern::ExistsQuery |
            QueryPattern::SubqueryExists => {
                hints.use_prepared_statement && hints.complexity != QueryComplexity::Complex
            },

            // Only cache complex queries if explicitly recommended
            QueryPattern::NestedSubquery |
            QueryPattern::UnionQuery |
            QueryPattern::ComplexQuery => {
                hints.cache_result && 
                hints.use_prepared_statement && 
                hints.complexity == QueryComplexity::Medium
            },
        }
    }
    
    /// Check if query might need binary protocol support (return false to use fallback)
    fn supports_binary_protocol(&self, query: &str) -> bool {