False positive while comparing sql files.

[Steven]

I am comparing two versions of various .sql file that contains a CREATE TABLE statement.

I have a ruleset created for .sql files that ignores case, and most lines are correctly ignoring case differences.

All of the columns in this create table have different by case only. The file on the left is all uppercase for each column name and on the right they are mixed case.

For example on the left.
[LASTDATETIME] DATETIME NULL,

And on the right.
[LastDateTime] DATETIME NULL,

Most lines are correctly not showing as different becasue only the case is different however in each file I compare I get a few lines that show diffreneces like this sample.

Any idea why these false positives are occuring?

Thanks
Steven

[jeffhostetler]

This is a bug.

This is happening because DiffMerge is only using the ignore-case setting to
vertically align the lines. (Within the line, it uses the show/hide importance
setting to decide whether to highlight the differences.)

The reason you're seeing the colorings is because the 'A' is sync'ing up with the 'ate'
and the 'T's are sync'd up and then the 'ETIME' is sync'ing up with 'ime'. The confusion
is because there are 2 'T's in DATETIME and the alignment is off.

What I need to do to fix this is to have the intra-line sync-up also use the ignore-case
settings before the show/hide stuff kicks in.

Sorry, I don't have a solution for you right now.

I've logged this at item:14140.

jeff

[Steven]

Version 3.3.0 (18513) still has this issue.

Do you have a guess when a solution or work around for this issue might be available.

Thanks
--Steven

[jeffhostetler]

sorry, but no. we haven't talked about scheduling for the next DiffMerge release yet.
so i don't know if it'll be a 3.3.1 or a 3.4.0 and/or what it will/won't have in it. if i had
to make a SWAG, i'd like to have something out in the 9 months from now time frame,
but again, that's just a guess.

sorry i can't be more helpful at this time.

jeff