StrByCharset – PB Docs 2019

Description

Specifies how to convert string data between PowerBuilder Unicode
strings and multibyte strings on the client.

Applies to

I10 Informix

O90 Oracle9i

O10 Oracle 10g

ORA Oracle (for 11g and later)

Syntax

Default value

StrByCharset=0

Usage

Informix

The StrByCharset DBParm specifies how to convert string data
between PowerBuilder Unicode strings and Informix client multibyte
strings. By default, string conversion for UTF-8 code sets is based on
the UTF-8 code set, and string conversion for non-UTF-8 code sets is
based on the current OS code page. If StrByCharset is set to 1 (true),
string conversion is based on the code set specified in the DBParm
Client_Locale.

Example 1

With these settings:

The Informix client and server character sets match, so all string
data from the client can be sent to the server and fetched back
directly, even if some characters do not belong to the EN_US.8859-1
character set but are within code page 1252, because no string
conversion happens between the Oracle client and server. All string data
can be displayed using the OS code page. If StrByCharset is set to 1,
when string data is converted between the Informix client (ANSI) and
PowerBuilder (Unicode), characters that are not in the EN_US.8859-1
character set are not converted correctly.

Example 2

With these settings:

The client and server character sets match. All string data,
including Korean characters, are sent or received one byte at a time so
no data is lost. Using the Korean OS code page, all Korean string data
can be converted from ANSI to Unicode safely with StrByCharset set to
0.

Example 3

With these settings:

Because characters in the ZH_TW.BIG5 character set do not belong
to code page 1252, string data conversion must be based on the
ZH_TW.BIG5 character set.

Oracle

The StrByCharset DBParm specifies how to convert string data
between PowerBuilder Unicode and OCI client multibyte strings. By
default, string conversion is based on the current OS code page or an
Oracle character set. The StrByCharset database parameter is ignored if
NLS_Charset is set to Unicode because both PowerBuilder and the OCI
client use the UTF-16 format. When NLS_Charset is set to another value,
you must set StrByCharset to 1 if the character set on the client is
incompatible with the OS code page.

Example 1

With these settings:

The Oracle client and server character sets match, so all string
data from the client can be sent to the server and fetched back
directly, even if some characters do not belong to the WE8ISO8859P1
character set but are within code page 1252, because no string
conversion happens between the Oracle client and server. All string data
can be displayed using the OS code page. If StrByCharset is set to 1,
when string data is converted between the OCI client (ANSI) and
PowerBuilder (Unicode), characters that are not in the
WE8ISO8859P1character set are not converted correctly.

Example 2

With these settings:

The client and server character sets match. All string data,
including Korean characters, is sent or received one byte at a time so
no data is lost. Using the Korean OS code page, all Korean string data
can be converted from ANSI to Unicode safely with StrByCharset set to
0.

Example 3

With these settings:

Because characters in the ZHT16BIG5 character set do not belong to
code page 1252, string data conversion must be based on the ZHT16BIG5
character set.

Examples

To specify that the Informix client should use the fr_FR.8859-1
character set defined by the Client_Locale parameter to handle string
datatypes:

To specify that the OCI client should use the character set
defined by the NLS_LANG parameter on the local computer to handle string
datatypes:

See also

Client_Locale

Db_Locale

NLS_Charset