This repository has been archived by the owner on Oct 13, 2021. It is now read-only.
Add profiling ability for SQL queries. #49
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Appending "&explain=true" to the end of the URL of any query will run the query as normal but not return the results to the browser. Instead it will report the results of "EXPLAIN QUERY PLAN" for every SQL statement that is run along with the time that each statement took. This can be useful in diagnosing slow queries and figuring out how to speed them up.
ehsan
added a commit
that referenced
this pull request
Jan 2, 2013
Add profiling ability for SQL queries.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Appending "&explain=true" to the end of the URL of any query will run
the query as normal but not return the results to the browser.
Instead it will report the results of "EXPLAIN QUERY PLAN" for every
SQL statement that is run along with the time that each statement took.
This can be useful in diagnosing slow queries and figuring out how to
speed them up.