Gbase8s database specifies the comparison order with set collation

For all database servers previously accessed in the current session ,SET COLLATION With locale The specified comparison order replaces when

The comparison order before . for example , This example specifies the comparison order of Chinese ：

EXEC SQL set collation “zh_cn.gb18030-2000”;

If the activity of the next database server in this session is right NCHAR or NVARCHAR sorted , Follow the Chinese

Comparison order .

In the same conversation , Assume the following SET NO COLLATION The statement restores the DB_LOCALE Set up ：

EXEC SQL set no collation;

stay SET NO COLLATION After performing , Subsequent comparisons in the same session are based on this DB_LOCALE Set up . however

and , Any database object you create in Chinese cross reference order , Such as checking constraints 、 Indexes 、 Ready objects 、 Trigger or

UDR, Will continue to apply Chinese comparison to NCHAR and NVARCHAR data type .

stay NLSCASE INSENSITIVE Comparison in the database

stay NLSCASE INSENSITIVE In the database , stay NCHAR and NVARCHAR The comparison operation on the data does not distinguish words

Parent case , So that the database server will repeat the case variables in the string composed of letters with the same sequence as the string

Handle . The cross reference list arranges these case sensitive repeated contents according to the order in which they are retrieved , therefore , With a string

alpha The list of comparisons of case variables of may appear in any order , For example, the following sequence , Regardless of the case of variables ：

alpha

Alpha

alpha

ALPHA

Alpha

For more information , see also stay NLSCASE INSENSITIVE Duplicate rows in the database and In case sensitive data

In the library NCHAR and NVARCHAR expression .