Comments
Sort by recent activity
This is still an issue in 9.2.9. Here is an example with multiple BEGIN statements: BEGIN
BEGIN
BEGIN
IF @Country = 'USA' BEGIN
SET @FormatCode = 1;
END;
ELSE BEGIN
SET @FormatCode = 2;
END;
END;
END;
END;As you can see, the SET statements have no indentation at all. I would like to automate style checks around the style guide I posted, but until this error is addressed we cannot, since it would undo the manual fixes around this problem. / comments
This is still an issue in 9.2.9. Here is an example with multiple BEGIN statements:BEGIN
BEGIN
BEGIN
IF @Country = 'USA' BEGIN
SET @FormatCode = 1;
END;
ELSE BEGIN
SET @FormatCode = 2;
...
This is part of a stored procedure. I only cut out the place where RedGate SQL Prompt was failing to produce expected results. So the whole thing was indented at least once from the BEGIN / END around the entire PROC, and likely indented again since I believe it was in an IF BEGIN / END block as well. This also used to work as expected in a previous version of SQL Prompt, in that the statements enclosed in the BEGIN / END statements aligned with the N in the BEGIN (one tab over) Here is a sample from the last working SQL Prompt version: IF dbo.DATEONLY(@EndDate) = dbo.MONTHEND_DATEONLY(@EndDate)
BEGIN
IF @StartDate IS NULL SET @StartDate = DATEADD(mm, -3, dbo.MONTHBEGIN(@EndDate));
END;
ELSE BEGIN
IF @StartDate IS NULL SET @StartDate = DATEADD(dd, -1, @EndDate);
END;Well at least it looks correct in SSMS, where a tab is equivalent to 4 spaces. / comments
This is part of a stored procedure. I only cut out the place where RedGate SQL Prompt was failing to produce expected results. So the whole thing was indented at least once from the BEGIN / END aro...
Yes, perhaps it would be easier to see with images: Before: [image] After: [image] The problem is that the SET statements have no tabs preceding them, when they should have 2 tabs each. This is using my custom style sheet, although you can see a similar but different problem using the collapsed style sheet: [image] In this one it is using spaces instead of tabs, but the same problem is present on the first SET statement, in that there are no spaces or tabs. / comments
Yes, perhaps it would be easier to see with images:Before:After:The problem is that the SET statements have no tabs preceding them, when they should have 2 tabs each.This is using my custom style s...
I see it correctly on my screen. Let me try another time. Here is what is currently happening: IF @Country = 'USA' BEGIN
SET @FormatCode = 1;
END;
ELSE BEGIN
SET @FormatCode = 2;
END; And here is what should be happening / what did happen in previous versions: IF @Country = 'USA' BEGIN
SET @FormatCode = 1;
END;
ELSE BEGIN
SET @FormatCode = 2;
END;<br> / comments
I see it correctly on my screen. Let me try another time.Here is what is currently happening: IF @Country = 'USA' BEGIN
SET @FormatCode = 1;
END;
ELSE BEGIN
SET @FormatCode = 2;
END;And here is ...
There was a problem I had, with misaligned parameter default values, which they said was broken in version 9.1.1.4243. It has subsequently been fixed, but I've found a new error, with misaligned blocks I am trying to get resolved now. I am thinking it might be best to go back to a earlier 9.1 version as well. / comments
There was a problem I had, with misaligned parameter default values, which they said was broken in version 9.1.1.4243. It has subsequently been fixed, but I've found a new error, with misaligned bl...
It is still an issue with the current version, and you can reproduce it with just the following:
CREATE TABLE dbo.Product (
SupplierID INT,
ProductID SMALLINT,
CategoryId SMALLINT,
DateActive DATETIME,
DateInactive DATETIME,
PackageOnly BIT,
BundleOnly BIT,
PRIMARY KEY (SupplierID, ProductID)
);
GO
DECLARE @SupplierID INT, @ProductCategoryID SMALLINT, @LastDate DATETIME, @ArrivalDateTime DATETIME;
SELECT *
FROM dbo.Product p
WHERE p.SupplierID = @SupplierID
AND p.CategoryId = @ProductCategoryID
AND p.DateActive <= @LastDate
AND p.DateInactive >= @ArrivalDateTime
AND p.PackageOnly = 0
AND (p .BundleOnly IS NULL OR p.BundleOnly = 0); / comments
It is still an issue with the current version, and you can reproduce it with just the following:
CREATE TABLE dbo.Product (
SupplierID INT,
ProductID SMALLINT,
CategoryId SMALLINT,
DateActive D...
khkiley wrote: »
@Matthew_Sontum Try changing your alias to multiple characters from a single character. This workaround has been working for me.
K
There was no difference / comments
khkiley wrote: »
@Matthew_Sontum Try changing your alias to multiple characters from a single character. This workaround has been working for me.
K
There was no difference
It won't let me attach it to the forum, so I have sent it to the email address. / comments
It won't let me attach it to the forum, so I have sent it to the email address.
Has this been resolved? I am using SQL Compare 13 and I still have a similar issue. In my database project I have the line: ALTER TABLE [dbo].[Person] ENABLE CHANGE_TRACKING WITH (TRACK_COLUMNS_UPDATED = OFF); And yet in the comparison it displays as: ALTER TABLE [dbo].[Person] ENABLE CHANGE_TRACKING WITH (TRACK_COLUMNS_UPDATED = ON) And is thus a conflict when compared against the database, where it lists the ALTER statement as: ALTER TABLE [dbo].[Person] ENABLE CHANGE_TRACKING / comments
Has this been resolved? I am using SQL Compare 13 and I still have a similar issue. In my database project I have the line:ALTER TABLE [dbo].[Person] ENABLE CHANGE_TRACKING WITH (TRACK_COLUMNS_UPDA...