The issue here is not that it doesn't equate to any other character (outside of a binary collation), and in fact it actually does equate to one other character ( U+0312 Combining Turned Comma Above): WITH nums AS They added a lot of sort weights and uppercase/lowercase mappings in the 100 series that aren't in the 90 series, or the non-numbered series, or the mostly obsolete SQL Server collations (those with names starting with SQL_). Now, anyone using SQL Server 2008 or newer should be using a 100 (or newer) level collation. SELECT REPLACE(N'a˚aa' COLLATE Latin1_General_100_CI_AS, N'a˚', N'_') - Returns _aa For example, the following character (U+02DA Ring Above) behaves slightly differently depending on which side of a character it is on: SELECT REPLACE(N'a˚aa' COLLATE Latin1_General_100_CI_AS, N'˚a', N'_') - Returns a_a ![]() This behavior is not specifically a "problem", though yes, there are other characters that exhibit similar behavior. It is not "weird" behavior: it's just not what you were expecting. ![]()
0 Comments
Leave a Reply. |