Claus Pedersen
Member³
I am aware that most of these change requests have been proposed in the beta forum, but I would like to have a general view on these from other users in the general PLD forum.
The points are listed in order of priority with the most wanted first.
1. Please change the debugger result set window into more like the normal SQL window, so selects can be entered and executed and the results can be seen in the same window.
Now, a small pop-up window is displayed where the SQL can be entered. If you make syntax errors, the window is closed with an error message and you must activate the Execute SQL button again to correct the error. Not very user-friendly.
The debugger windows should be like the normal SQL window:
A pane at the top where SQL can be entered and corrected and changed.
A yellow gear icon button to execute the SQL.
A possibility to export the query results (enable the Export query results button)
2. The result grid in the debugger result set window does not have focus. You can not use the arrow keys or PgUp or PgDown keys to navigate to rows or items without first activating the focus using the mouse.
3. An optional limitation of how many rows are fetched (a number in the screen, just like DBMS output buffer size can be changed in the normal SQL window). Queries returning more than e.g. 1000 rows take a very long time to execute (at least on my database).
4. There should be an option to set the NLS_DATE_FORMAT in the debug session SQL window, so dates are shown in the same way as in the normal SQL window (in my case also with time fraction).
I know the user could set NLS_DATE_FORMAT by hand (either directly as a part of the test code or in the logon script), but it would be more convenient that PLD did this 'behind the scene'.
5. The spawned debugger result set window(s) should be closed when the originating test window is closed (or the user should at least be asked, whether the windows should be closed).
6. Show a busy cursor icon (hour glass) when the query is executing after having pressed F8 to execute. Today you can not see that anything is happening (in other ways that the PLD is not responding).
7. There should be a visual link between the test window, where the debugger result set originates from (show the first couple of lines from the test window in the title of the debugger result set window or similar).
8. The length of the select shown in the window title is limited to the first 80 characters of the SQL and on most screen resolutions, there is room for a lot more, in my screen resolution, at least the double amount.
Also, please indicate by [...] or similar at the end of the query string, that is has been truncated. Especially in long where clauses, it would be good to have a hint that something has been left out.
The points are listed in order of priority with the most wanted first.
1. Please change the debugger result set window into more like the normal SQL window, so selects can be entered and executed and the results can be seen in the same window.
Now, a small pop-up window is displayed where the SQL can be entered. If you make syntax errors, the window is closed with an error message and you must activate the Execute SQL button again to correct the error. Not very user-friendly.
The debugger windows should be like the normal SQL window:
A pane at the top where SQL can be entered and corrected and changed.
A yellow gear icon button to execute the SQL.
A possibility to export the query results (enable the Export query results button)
2. The result grid in the debugger result set window does not have focus. You can not use the arrow keys or PgUp or PgDown keys to navigate to rows or items without first activating the focus using the mouse.
3. An optional limitation of how many rows are fetched (a number in the screen, just like DBMS output buffer size can be changed in the normal SQL window). Queries returning more than e.g. 1000 rows take a very long time to execute (at least on my database).
4. There should be an option to set the NLS_DATE_FORMAT in the debug session SQL window, so dates are shown in the same way as in the normal SQL window (in my case also with time fraction).
I know the user could set NLS_DATE_FORMAT by hand (either directly as a part of the test code or in the logon script), but it would be more convenient that PLD did this 'behind the scene'.
5. The spawned debugger result set window(s) should be closed when the originating test window is closed (or the user should at least be asked, whether the windows should be closed).
6. Show a busy cursor icon (hour glass) when the query is executing after having pressed F8 to execute. Today you can not see that anything is happening (in other ways that the PLD is not responding).
7. There should be a visual link between the test window, where the debugger result set originates from (show the first couple of lines from the test window in the title of the debugger result set window or similar).
8. The length of the select shown in the window title is limited to the first 80 characters of the SQL and on most screen resolutions, there is room for a lot more, in my screen resolution, at least the double amount.
Also, please indicate by [...] or similar at the end of the query string, that is has been truncated. Especially in long where clauses, it would be good to have a hint that something has been left out.
