We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Sqlcheck does not show line number on which antipattern or hint is reported . Currently it gives following format
[D:\temp_func.sql]: (LOW RISK) (QUERY ANTI-PATTERN) Spaghetti Query Alert [Matching Expression: ]
[D:\temp_func.sql]: (LOW RISK) (QUERY ANTI-PATTERN) UNION Usage [Matching Expression: union]
can it give line no as well ? e.g . [D:\temp_func.sql]: (LOW RISK) (QUERY ANTI-PATTERN) UNION Usage [Matching Expression: union] [34]
This becomes very useful when it is a huge file. With line number (starting position of the query) you can directly navigate to the specific query.
Line number are very common in all code checker , as they give better user experience .
Should line number be added here?
Thanks
The text was updated successfully, but these errors were encountered:
dzsquared
No branches or pull requests
Sqlcheck does not show line number on which antipattern or hint is reported . Currently it gives following format
[D:\temp_func.sql]: (LOW RISK) (QUERY ANTI-PATTERN) Spaghetti Query Alert
[Matching Expression: ]
[D:\temp_func.sql]: (LOW RISK) (QUERY ANTI-PATTERN) UNION Usage
[Matching Expression: union]
can it give line no as well ?
e.g . [D:\temp_func.sql]: (LOW RISK) (QUERY ANTI-PATTERN) UNION Usage
[Matching Expression: union] [34]
This becomes very useful when it is a huge file. With line number (starting position of the query) you can directly navigate to the specific query.
Line number are very common in all code checker , as they give better user experience .
Should line number be added here?
Thanks
The text was updated successfully, but these errors were encountered: