Top
Symfoware Server V12.1.0 Application Development Guide
FUJITSU Software

A.6 Notes on Using Multibyte Characters in Definition Names

Do not use multibyte characters in database names or user names if using a Windows database server.

Multibyte characters must not be used in database space names or user names on non-Windows database servers, because certain conditions may apply or it may not be possible to connect to some clients.

Related notes and constraints are described below.

1) Configuring the client encoding system

The client encoding system must be configured when the names are created.

See

Refer to "Character Set Support" in "Server Administration" in the PostgreSQL Documentation for information on how to configure the client encoding system.

2) Encoding system of names used for connection

Ensure that the encoding system of names used for connection is the same as that of the database that was connected when these names were created.

The reasons for this are as follows:

Accordingly, if the database that was connected when the names were defined uses the EUC_JP encoding system, but the database name is specified using UTF-8 encoding, then the database will be considered to be non-existent.

3) Connection constraints

The table below shows the connection constraints for each client type, based on the following assumptions:

Client type

Client operating system

Windows

Linux

JDBC driver

Cannot be connected

Cannot be connected

ODBC driver

Cannot be connected

No connection constraints

.NET Data Provider

Can only connect when the encoding system used for definitions is UTF-8

-

SQLEmbedded SQL in C

Can only connect when the connection service file (pg_service.conf) is used

No connection constraints

psql command

Can only connect when the connection service file (pg_service.conf) is used

No connection constraints