Activity overview
Latest activity by opc.three
Indeed it was. I was on build 300. Build 315 has the fix. Thanks. / comments
Indeed it was. I was on build 300. Build 315 has the fix. Thanks.
BUG: incorrect alias attempt
IF EXISTS ( SELECT c.name as column_name
FROM sys.schemas s
JOIN sys.tables t ON s.schema_id = t.schema_id
JOIN sys.columns c ON...
Anyone know the status of SC-2456 (mentioned by peter.peart in a 2012 post on this thread)? / comments
Anyone know the status of SC-2456 (mentioned by peter.peart in a 2012 post on this thread)?
I cannot post the entire query however I did revisit this and see there is additional info when I hover over the red squiggly underline, it says:
The column SomeID could not be resolved as a column with that name exists in multiple tables
The use of the English language in the error message is dreadful however I made sure to type it in exactly as it is shown, i.e. that is the exact error message shown.
By me adding a "target."-qualification to the column SomeID in my original code the error goes away however this should not be necessary because SQL Server does not require it, i.e. it is unambiguous so SQL Prompt should not complain. By definition "WHEN NOT MATCHED BY SOURCE" any additional predicates can only be referring to the target otherwise the predicate would be trivial. WHEN NOT MATCHED BY SOURCE AND SomeID = @SomeID THEN DELETE
I have overcome the issue but I still think SQL Prompt should relax on this validation to match SQL Server. / comments
I cannot post the entire query however I did revisit this and see there is additional info when I hover over the red squiggly underline, it says:
The column SomeID could not be resolved as a colum...
AndrewPierce wrote:
SQL Prompt does not underline errors, that is done directly by SSMS' Intellisense.
Hi again Andrew. I think the wires are getting crossed somehow. The underlining (or highlighting as SQL Prompt calls it) occurs after I attempt to format the code using SQL Prompt, e.g. pressing Ctrl+K, Ctrl+Y. The underline is a wavy red line and the error message is exactly:
SQL Prompt was unable to complete this operation.
Problem areas have been highlighted.
To confirm, I have SSMS Intellisense disabled when this occurs.
I hope this clarifies the issue.
Hopefully this issue is not limited to my machine. If you would try formatting my repro code with my style settings using my version of SQL Prompt hopefully you can see what I see. / comments
AndrewPierce wrote:
SQL Prompt does not underline errors, that is done directly by SSMS' Intellisense.
Hi again Andrew. I think the wires are getting crossed somehow. The underlining (or highli...
Error formatting MERGE statement in WHEN NOT MATCHED BY
WHEN NOT MATCHED BY SOURCE AND SomeID = @SomeID THEN DELETE
The above code inside a MERGE statement is giving SQL Prompt problems causing it to show a Syntax error underlining column SomeID.
Error when formatting otherwise valid SQL with subqueries
Repro:USE tempdb;
CREATE TABLE #tmp (id INT, name VARCHAR(100))
CREATE TABLE #tmp2 (id INT, name VARCHAR(100))
DELETE FROM #tmp
WHERE id = (
SELECT id
FROM ...
Manage multiple Extended Properties, not just MS_Description
I am evaluating SQL Doc and am curious if there is a way to have the tool allow us to edit Extended Properties besides only the one named MS_Description. At present it is displaying other named pro...
"Find Unused Variables and Parameters" at command line
I am a big fan of SQL Prompt! The "Find Unused Variables and Parameters" feature is very useful and has allowed us to clean up many wasteful declarations as we work on existing objects. All of our ...