Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DROP IF EXISTS syntax doesn't appear to be supported
See original GitHub issueSQL Server 2016 introduced DROP [VIEW|TABLE|PROCEDURE|FUNCTION] IF EXISTS syntax.
TSqlLint is reporting these as syntax errors i.e.:
NoticesView.sql(1,11): error invalid-syntax : Incorrect syntax near IF..
and this isn’t configurable via the rules.
It looks like the TSqlLint tool uses the Microsoft.SqlServer.TransactSql.ScriptDom package so it might be that this cannot actually be solved without Microsoft updating their package unfortunately, and I’m not sure that is even still maintained…
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi, very much appreciate you putting in the work to implement the configurable parser feature! Myself and a colleague had identified that TSql120Parser was being instantiated in FragmentBuilder; we downloaded your source code, saw that there was a TSql140Parser class as well, rebuilt with that change, and it worked for us… I was about to reply on this thread to suggest this but you fixed it already 😃 Just wondering if there is a reason why your compatibility level list only covers up to 130 and not 140 (although this should be fine for us since that 130 = SQL Server 2016 I believe)?
140 (sql server 2017) was not intentionally left out, I just pulled the levels from an out of date chart. 140 should be supported as well, #172 for tracking.
I very much appreciate you bringing this to our attention!