SQL Compare missed a difference between two stored procedures

SQL Compare missed a stored procedure where there was a space before a colon - see attached. 2oljjnf1uylz.png
Tagged:

Best Answer

Answers

  • ebwindebwind Posts: 2 New member
    Thanks Sam, that was it.
  • Chris_FChris_F Posts: 12 Bronze 1
    If that fixed it then that definitely should be a bug.

    White-space should be classed as the white-space around statements, not within a literal string.

    If a statement is preceded with 2 tabs instead of one that's no issue, but if there is a string/code different then that is a major issue if it gets missed.

    SQL Compare should be smart enough to pick up the difference between the two.

Sign In or Register to comment.