You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, when one issues a query, there are no metrics for how long the query took to execute or how many rows it returns. Since this may be in the way of the pipeline, perhaps it'd be fine to stash the metrics or out-of-rows metadata somewhere for fetching with another command.
query "SELECT foo FROM bar LIMIT 1"
(…pipeline renders table)
query lastmetrics
(…pipeline renders table)
There might be better solutions too, like a setting for getting metrics in the pipeline too which I think will generate another output. Or a flag and a setting.
The text was updated successfully, but these errors were encountered:
At the moment, when one issues a query, there are no metrics for how long the query took to execute or how many rows it returns. Since this may be in the way of the pipeline, perhaps it'd be fine to stash the metrics or out-of-rows metadata somewhere for fetching with another command.
There might be better solutions too, like a setting for getting metrics in the pipeline too which I think will generate another output. Or a flag and a setting.
The text was updated successfully, but these errors were encountered: