|
Wondering if anyone would find this useful: when a ISQL Error pops up listing 'Syntax error near ',' on line 345....' I believe it would be helpful to have a listed number sequence on the left hand side of the error window similiar to the numbered sequence in the SQL Statements window in ISQL. When the query has lots of lines, spaces, etc, it's tough to track down the offending line unless you count down from the top. What say? Any other suggestions? |
|
Line numbers in the error dialog is great idea. We'll try to get that into a future release. About carolstone's comment -- DBISQL 12.0.0 and later does exactly what you describe. |
I agree, ESPECIALLY since the line number reported is counted from the top of the code in the error window, which is NOT necessarily the same as the top of the code in the ISQL edit window. The numbers diverge if ISQL is compiling multiple statements or batches; the error number refers to the current batch being compiled. ALSO, the error window should not be a modal response window, or if that is too difficult (since it is expecting a response), there should be a button to hive off a separate non-modal window containing the same information... or an error pane in the main display.
(more) This stuff aggravates me many times a day as I run giant multi-file builds using ISQL.
I can't believe it never occurred to me to wish for line numbers. I've often found myself wishing my cursor would just jump to the offending location when I click 'ok' to the dialog. The big exception to that wish, of course, is when the location turns out to be the end of all of my statements.