guttormvik
Member²
Just tried to run two large selects.
Cursor was at the end of the 2nd statement.
When I pressed F8, Plyxon started to run the 1st statement, but it was showing the "result" of the 2nd one; ie nothing.
It looked like nothing was happening, or that it was frozen.
If you are going to keep this way of doing it, you should probably have a status-icon on the blocks to show what has run / is running / has failed..
Ie, what you do on the result tabs in todays pl/sql developer.
I think I would prefer the old way of having result tabs. The way it is now, it is harder to write a statement and use values from the result of a previous statement.
Looks like you are immediately fetching all rows, instead of fetching just the first page".
Not sure what I think about that. I often do "select * from x" to get a sense of the structure. It rarely makes sense for me to view all the, say, 400K rows. *Sometimes* I want that, but I don't think it should be the default. Now I have to remember to kill it. Again, I think pl/sql developer strikes the right balance.
When I *had* fetched all the 400K rows, Plyxon had increased 1G in size. This did not disappear when I added a where-clause to fetch 0 rows and re-ran it.
It did, however, disappear when I closed the tab.
Cursor was at the end of the 2nd statement.
When I pressed F8, Plyxon started to run the 1st statement, but it was showing the "result" of the 2nd one; ie nothing.
It looked like nothing was happening, or that it was frozen.
If you are going to keep this way of doing it, you should probably have a status-icon on the blocks to show what has run / is running / has failed..
Ie, what you do on the result tabs in todays pl/sql developer.
I think I would prefer the old way of having result tabs. The way it is now, it is harder to write a statement and use values from the result of a previous statement.
Looks like you are immediately fetching all rows, instead of fetching just the first page".
Not sure what I think about that. I often do "select * from x" to get a sense of the structure. It rarely makes sense for me to view all the, say, 400K rows. *Sometimes* I want that, but I don't think it should be the default. Now I have to remember to kill it. Again, I think pl/sql developer strikes the right balance.
When I *had* fetched all the 400K rows, Plyxon had increased 1G in size. This did not disappear when I added a where-clause to fetch 0 rows and re-ran it.
It did, however, disappear when I closed the tab.
