Competition: What’s your favorite Redgate tool? Enter now.

XML Element case-sensitive, change not recognized by SSC

PDinCAPDinCA Posts: 642 Silver 1
Changing an XML element name in a xml.query() from PriorTierCanAccept to priorTierCanAccept in multiple SPs is not recognized as a change by SSC.

Perhaps SSC should IGNORE the DATABASE case-sensitivity and treat text as text: find any change to be significant enough to update the repository.
Jesus Christ: Lunatic, liar or Lord?
Decide wisely...


  • Brian DonahueBrian Donahue Posts: 6,590 New member

    This sounds fair. You'll want database collation to be considered normally, but XML is usually case-sensitive, so any queries would be broken if the case was incorrect. I've logged a bug SC-6039 about this. I can't promise anything though. It doesn't sound like it would be trivial to implement.
  • Any update on this? I posted in another thread about this (for varchar, not XML). Ideally even on case insensitive collated databases, changed-case string could be committed and transferred to other devs via SSC. I've even tried tricking it by updating a second field (like a datestamp). The behavior is that the other dev gets the new date value but the string value is left unchanged.

    But the INSERT statements stored in the static data script in svn are picking up the correct case.
Sign In or Register to comment.