Neoview Character Sets Administrator's Guide (R2.4, R2.5)

Behavior of SQL String Functions
String functions behave differently in the Neoview Release 2.3 and Neoview Release 2.4
environments. Table 3-3 describes these differences.
Table 3-3 String Function Behaviors for Neoview Release 2.3 and Neoview Release 2.4
Storage Length vs. Character BoundariesLimitationsNeoview Release
Position and length used by string functions
determine the storage length, not character
boundaries. For example, single-byte
characters use one character for string
functions, while 2-byte characters require two
characters.
String functions might not work properly
when input strings containing multibyte
characters are stored in ISO88591 columns on
a Neoview platform using the SJIS or Unicode
configuration.
Release 2.3
Character boundaries determine character
units. Each single-byte and multibyte
character is treated as one character for string
functions, no matter the byte length of the
character.
String functions that contain valid multibyte
characters can be stored in SQL table columns
when using SJIS characters in the SJIS
configuration or UTF8 characters in the
Unicode configuration without causing data
corruption. If an invalid character is used, an
error is returned.
Release 2.4
Table 3-4 describes the SQL string functions and, where applicable, unique considerations for
the ISO88591, SJIS, and Unicode configurations. SQL string function values can be provided to
table columns in the form of a literal or a parameter.
Behavior of SQL String Functions 27