Closed
Description
Is your feature request related to a problem? Please describe.
While developing and running a query, it is possible to have 0 results in the formatted alerts table, but a non-zero number of tuples in the #select table. This can happen if the selected entity is missing location information, or if there is a mismatch between the query metadata and the columns in the select clause. This commonly trips up both new and experienced writers and leads to time wasted debugging the query's logic.
Describe the solution you'd like
- Make it obvious to the user how many results are in each of the result tables, regardless of which result table is currently being displayed in full.
- Suggest the user checks the query metadata/result patterns if there is a mismatch with 0 alerts.
Describe alternatives you've considered
Alternatively, make 0 alerts a special case, and in this case have an annotation pointing the user to the #select table or the table dropdown.
Additional context