Allow setting globals for `analyze` command
Open
- Dominant language
- Rust
- Stars
- 175
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
Many queries require globals to be set to really understand the performance, but there is no easy way to provide globals with the `edgedb analyze` command. While it is currently possible to run a REPL session to analyze query performance with globals, sometimes the output is too large to reasonably fit in a terminal window, so it would be more convenient to pipe the output to a file for analysis.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.