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

Table 3-4 Behaviors of SQL String Functions in the Three Configurations (continued)
Unicode Configuration
Considerations
SJIS Configuration
Considerations
ISO88591
Configuration
ConsiderationsSQL String Function and Description
• The UTF8TOUCS2
option can be used
to translate UTF8
characters in an
ISO88591 column to
UCS2 characters.
• The UCS2TOUTF8
option can be used
to translate UCS2
characters to UTF8
characters.
• The
ISO88591TOUCS2
option can be used
to translate
ISO8859-1
characters to UCS2
characters.
• The
UCS2TOISO88591
option can be used
to translate UCS2
characters to
ISO8859-1
characters.
• The SJISTOUCS2
option can be used
to translate SJIS
characters in an
ISO88591 column
to UCS2
characters.
• The UCS2TOSJIS
option can be used
to translate UCS2
characters in a
UCS2 column to
SJIS characters.
• The
ISO88591TOUCS2
option can be used
to translate
ISO8859-1
characters to UCS2
characters.
• The
UCS2TOISO88591
option can be used
to translate UCS2
characters to
ISO8859-1
characters.
• The
ISO88591TOUCS2
option can be used
to translate
ISO8859-1
characters to UCS2
characters.
• The
UCS2TOISO88591
option can be used
to translate UCS2
characters to
ISO8859-1
characters.
TRANSLATE: Translates a character string
from a source character set to a target
character set. These six
translation-name options can be used:
• ISO88591TOUCS2
• SJISTOUCS2
• UTF8TOUCS2
• UCS2TOISO88591
• UCS2TOSJIS
• UCS2TOUTF8
The TRANSLATE function changes both
the character string data type and the
character set encoding of the string.
Every character,
including multibyte
characters, is treated as
one character.
Every character,
including multibyte
characters, is treated
as one character.
Every character,
including multibyte
characters, is treated as
one character.
TRIM: Removes leading and trailing
characters from a character string.
No special
considerations
No special
considerations
No special
considerations
UCASE: Upshifts alphabetic characters. For
non-alphabetic characters, UCASE returns
the same character.
No special
considerations
No special
considerations
No special
considerations
UPPER: Same as UCASE.
No special
considerations
No special
considerations
No special
considerations
UPSHIFT: Same as UCASE.
Guidelines for the LIKE Predicate in the SJIS and Unicode Configurations
For customers with the SJIS or Unicode configuration, Neoview SQL Release 2.4 behaves
differently than Neoview Release 2.3 with respect to the LIKE predicate.
In Neoview Release 2.3, the underscore (_) matches only one byte. To use the underscore effectively
with multibyte characters, you must know the byte length of the multibyte character. Otherwise,
you might not get the results that you want using the LIKE predicate. If the Neoview platform
uses the SJIS configuration and you want to match one SJIS character, you must specify one or
two underscore characters in the LIKE pattern, depending on the number of bytes that make up
a single SJIS character. If the Neoview platform uses the Unicode configuration and you want
to match one UTF8 character, you must specify one to four underscore characters in the LIKE
pattern, depending on the number of bytes that make up a single UTF8 character.
Guidelines for the LIKE Predicate in the SJIS and Unicode Configurations 31