SQL Advanced Queries - Error Number Lines
1428
Views
24
Comments
On our RadarOn our Radar
Aggregates & Queries

I think that the line number where an error ocurrs, could be useful.

2014-02-07 17-02-43
Vasco Pessanha
Changed the category to
Aggregates & Queries
Merged this idea with 'Add line number' (created on 08 Jan 2020 15:42:31 by Thiago Mari)
2022-03-01 15-42-44
Thiago Mari
Champion

Hi,


I have a idea to add a collum with the line count at advance query. When if you get the error, in pop up message indicate the line number.


If you have a extend advance query, its more difficult to search the error



This comment was:
- originally posted on idea 'Add line number' (created on 08 Jan 2020 by Thiago Mari)
- merged to idea 'SQL Advanced Queries - Error Number Lines' on 08 Jan 2020 15:47:09 by Tiago Simões
2022-03-01 15-42-44
Thiago Mari
Champion

Is there any news about this idea?


Changed the status to
On our RadarOn our radar

Hi Thiago,

Not really. We might add line numbers to the editor (no promise, though). Having those on error messages might take a bit more effort. In any case I'll add this to our radar so we keep an eye on the evolution of this idea and eventually implement it in the future.

Cheers,
Tiago Simões

Merged this idea with 'Advanced Sql Line Number and error tracker' (created on 08 Oct 2021 05:30:04 by Aswin Parthiban)

If there is a line number in the sidebar of the advanced SQL widget and error

identifier, where the exact error is in by highlighting with red color. It would be more easily for identifying the errors and where the exact error is in which line number.   

Hi,

In the hybrid version of service studio, the SQL editor has line numbers.

Regards,

Daniel

Merged this idea with 'Show line number in Advance SQL Query' (created on 07 Sep 2021 14:13:14 by Krushna Mantri)

Hi Team,


Would be good to show the line number if any syntax error comes in Advance SQL while testing in Service Studio with the option as Test, like E.g. Incorrect Syntax on line 10 :

It would be very helpful to identify syntax errors quickly in large queries

Changed the category to
Aggregates & Queries
Merged this idea with 'Advanced SQL Meaningful Error Message' (created on 19 Jul 2022 08:47:19 by Sophie)

Most of the time it is difficult to debug complex queries in Advanced SQL due to the ambiguous error messages that happens when the developer tests the query. 

Therefore, as a suggestion a meaningful error message would be useful or at least point at the line number where the issue can be located.


Changed the category to
Aggregates & Queries
Merged this idea with 'Better error management for Advanced SQL queries' (created on 26 Oct 2022 10:00:13 by Philippe-Alexandre Pierre)

Hi everyone, 


It could be super useful to have more effective error management forAdvanced SQL queries. 

In the Service Studio, the error feedback should not appear in an alert message (too short, not explicit), but directly in the Output tab (or in a new Error tab), with the compiled request, the row and the column of the detected error.

The Monitoring screen in the Service Center should show the compiled request, the line and the column of the detected error. Currently, the query is in one line, truncated and the errors are not meaningful (especially when the error can be in different places because it is too vague).

That can be useful. Can help SQL debug.

It could be useful if the errors can be more specifically shown so as to fix it in less time.

Merged this idea with 'Go to feature for SQL Error' (created on 30 Aug 2023 07:07:49 by Akshay Deshpande)

It will be very grateful, If we have same feature in like .net or java code which redirect you to line or show you the line number with error

Right now its very difficult to finding those error if query is more than 10 line than its quite tough job to search and it also time consuming 

so better if we have feature like it will show direct line number or highlight the error part to make more user friendly 

YES! That could be nice. Mainly in big SQL queries.

Indeed! This seems a very useful idea!

Yes, it will be helpful and will save good amount of time.

It would be very helpful to have this info in the error message. It takes a couple of steps and some time to find the exact line number of the issue in current situation.