If you choose the UCA collation when you create a database, you can optionally specify collation tailoring options. If you do not choose UCA as the collation, you can still use tailoring syntax to control case sensitivity. You can also specify tailoring options when comparing or sorting data using the COMPARE and SORTKEY functions.
To tailor a UCA collation to conform to the Swedish Academy's 2005 standards in which V and W are considered to be different
characters at the primary level, specify UCA (locale=swe;sorttype=phonebook)
. Without sorttype=phonebook, V and W are considered to be the same character in the Swedish locale.
UCA distinguishes some Hiragana and Katakana letters only at the tertiary level and those differences are lost in case insensitive
collations. To tailor a UCA collation to define primary level differences between all Hiragana letters, as well as primary-level
differences between all Katakana letters, specify UCA (locale=ja;sorttype=direct;...)
. Although these tailoring options do not provide absolute correct sorting semantics, they do provide correct equality semantics.
Collation tailoring options take the form of keyword-value pairs. Following is a table of the supported keywords, including their allowed alternate forms, and their allowed values.
Databases created with collation tailoring options cannot be started using a pre-10.0.1 database server.
Keyword | Collation | Alternate forms | Allowed values |
---|---|---|---|
Locale | UCA | (none) | Any valid locale code. For example, en. |
CaseSensitivity | All supported collations | CaseSensitive, Case |
|
AccentSensitivity | UCA | AccentSensitive, Accent |
|
PunctuationSensitivity | UCA | PunctuationSensitive, Punct |
|
SortType | UCA | (none) |
The type of sort to use. Possible values include:
For more information about these sort types, see Unicode Technical Standard #35 at http://www.unicode.org/reports/tr35/. |
Discuss this page in DocCommentXchange.
|
Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1 |