pub fn execute_explain(
sel: &Select,
resolve: &Resolver<'_>,
exec: JoinExec,
) -> Result<(Vec<OutCol>, Vec<Value>, Plan)>Expand description
Run a parsed SELECT, also reporting how each join was executed.
exec forces a join strategy, which exists so that differential tests can
drive the SAME query down BOTH paths — and so a benchmark can prove it
measured the path it claims to have measured rather than silently timing
the other one twice.