In SQL Server, your ranges also need to ACCENT-uate the positives!

by Michael S. Kaplan, published on 2007/12/08 10:16 -05:00, original URI:

You might have started to sense a pattern developing here with the last few posts in this series:

That last post pointed out two characters that would be missing if you have a width sensitive collation.

and now this post is going to talk about accent sensitivity and it's impact.

This will add over two dozen characters like the following ones:

and more! All of which have some sort of "Z-ish" quality about them, none of which will be handled by the ranges defined thus far according to the documentation for SAL Server if your application is run in the context of an accent sensitive collation.


You get the point - this odd combination of actual linguistic characters used in language, phonetic symbols, and circled/parenthesize letters have a fundamental identity that users would expect to sort somewhere not far from the Z by default.

SQL Server does that well -- how about your application with your LIKE range? :-)

And just in case you thought I was done, it gets worse tomorrow....


This post brought to you by(U+24b5, aka PARENTHESIZED LATIN SMALL LETTER Z, the last Z-like thing in the Latin script....)

no comments

referenced by

2007/12/11 In SQL Server, there is the rest of Unicode (aka the SiaO Incompleteness Theorem)

2007/12/10 In SQL Server, different collations implies different ranges (aka Not every table has its THORN)

2007/12/09 In SQL Server, the alphabet does not end at Z!

go to newer or older post, or back to index or month or day