It's cool that you show the cursor's outputs as JSON-like data in the output window. But it's not cool that when I click on view button (eyeball) that the pane only shows “[object Object]” in it.
It's also not cool that you run all the cursors immediately as the rows stream in. That's slow…. And it could be bad (exceed max number of open cursors easily)….
Sample query (dumb example just to illustrate) and remove the where clause to see the performance penalty….
select
t.owner,
t.TABLE_NAME,
cursor(select tc.COLUMN_NAME, tc.DATA_TYPE from all_tab_columns tc where tc.owner = t.owner and tc.table_name = t.table_name) as cursor_test
from all_tables t
where t.table_name like 'ALL%';
I'd expect instead:
- do NOT run the cursors immediately. Render the output as some sort of button (the current eyeball view button makes sense)
- when the user clicks that button, run that cursor/query only at that point and display the output in a new query result pane (probably requires your solution to “show results of multiple queries” coming out soon)
Failing the above, in the very least, the pane that slides in should show the data better. I'd suggest showing it as JSON over the current internal representation that you are using (although really, I could just query that if it's what I want)….