Jonathan Taylor
Member²
If I run the following query
SELECT ROWNUM ID
FROM all_objects
ORDER BY 1
Then PLSD returns 100 rows - with IDs running from 1 to 100. Because these numbers don't need a wide column - the column is sized small.
If I then change the "ORDER BY 1" to "ORDER BY 1 DESC", I get the IDs in reverse order.
However, these "wide" numbers (highest is 23111 on my DB) are placed into a column the same width as the first query - they don't fit properly.
PLSD seems to have re-used the result grid from the first query. If I had done something to force a new grid (i.e. opened a new window, created an error between the 1st and 2sn query) - then the column would have been sized correctly.
SELECT ROWNUM ID
FROM all_objects
ORDER BY 1
Then PLSD returns 100 rows - with IDs running from 1 to 100. Because these numbers don't need a wide column - the column is sized small.
If I then change the "ORDER BY 1" to "ORDER BY 1 DESC", I get the IDs in reverse order.
However, these "wide" numbers (highest is 23111 on my DB) are placed into a column the same width as the first query - they don't fit properly.
PLSD seems to have re-used the result grid from the first query. If I had done something to force a new grid (i.e. opened a new window, created an error between the 1st and 2sn query) - then the column would have been sized correctly.
