I have a query
SELECT foo FROM bar WHERE some_column = ?
Can I get a explain plan from MySQL without filling in a value for the parameter?
A query is a request for data or information from a database table or combination of tables. This data may be generated as results returned by Structured Query Language (SQL) or as pictorials, graphs or complex results, e.g., trend analyses from data-mining tools.
The EXPLAIN statement provides information about how MySQL executes statements: EXPLAIN works with SELECT , DELETE , INSERT , REPLACE , and UPDATE statements. When EXPLAIN is used with an explainable statement, MySQL displays information from the optimizer about the statement execution plan.
To view a visual explain execution plan, execute your query from the SQL editor and then select Execution Plan within the query results tab. The execution plan defaults to Visual Explain , but it also includes a Tabular Explain view that is similar to what you see when executing EXPLAIN in the MySQL client.
Optimizing Queries with EXPLAIN According to the MySQL documentation, EXPLAIN works alongside SELECT, DELETE, INSERT, REPLACE, and UPDATE statements. It displays information from a built-in MySQL optimizer regarding the statement execution plan and the number of rows scanned in each table.
So long as you're doing only an equals (and not a like, which can have short circuit affects), simply replace it with a value:
EXPLAIN SELECT foo FROM bar WHERE some_column = 'foo';
Since it's not actually executing the query, the results shouldn't differ from the actual. There are some cases where this isn't true (I mentioned LIKE already). Here's an example of the different cases of LIKE
:
SELECT * FROM a WHERE a.foo LIKE ?
Foo
- Can use an index scan if an index exists.%Foo
- Requires a full table scan, even if an index existsFoo%
- May use an index scan, depending on the cardinality of the index and other factorsIf you're joining, and the where clause yields to an impossible combination (and hence it will short circuit). For example:
SELECT * FROM a JOIN b ON a.id = b.id WHERE a.id = ? AND b.id = ?
If the first and second parameters are the same, it has one execution plan, and if they are different, it will short circuit (and return 0 rows without hitting any data)...
There are others, but those are all I can think of off the top of my head right now...
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With