| After some discussion with Austin, we'd like to suggest some API changes. In particular, perhaps change the :explain?` parameter to :explain which would match the existing pretty, side-steps any questions about whether we'd want a question-mark in the query parameter name, or would need to change the name "on the way in", and also leave a convenient opening for future enhancements. In particular, we were thinking that perhaps this first version might only allow :explain :analyze rather than :explain true, under the argument that we might eventually want to allow other options, maybe like this:
https://...?explain=analyze |
https://...?explain=analyze,no_verbose,no_buffers |
https://...?explain=no_analyze
|
We might also process the comma-separated options from left to right so that later selections override earlier ones (which can be handy when programmatically generating queries:
https://...?explain=analyze,no_verbose,buffers,verbose
|
But we don't need any of that extended syntax for now (if ever). For now, we were thinking we might just implement explain=analyze (and internally :explain :analyze) and leave anything else for a hypothetical future. |
