Comments
5 comments
-
Hi @mattbenham
Sorry, you're experiencing this issue!
I can confirm I've been able to reproduce this in the latest version also, I'm going to verify this behavior with the development team and I'll let you know any updates! -
Perfect, thanks.
-
Hi @mattbenham
The team have mentioned using the following option "Use case-sensitive object definition"
I have tested this and it works for me! -
Thanks, that should do the trick. You may want to look at rewording the description next to that option as it is a little misleading as it only refers to object names, where in my case it was about a string literal.
-
Hi @mattbenham
I've passed that information along to the team, hopefully, everything will run smoothly for you now!
Add comment
Please sign in to leave a comment.
For example if you have a stored procedure that simply executes "SELECT 'TEST' " and then change "TEST" to lower case, SQL Source Control does not detect the change.
I had an example where an external partner needed a subtle case change in an XML string generated by a stored procedure. I had to make a superfluous minor change to the SP to get Source Control to detect and commit the intended change.