Understanding locales
324
•
Which language to request from the database.
For more information, see “Understanding the locale language” on page
324.
•
Character set
The character set is the code page in use. The client and
server both have character set values, and they may differ. If they differ,
character set translation may be required to enable interoperability.
For machines that use both OEM and ANSI code pages, the ANSI code
page is the value used here.
For more information, see “Understanding the locale character set” on
page 325.
•
Collation label
The collation label is the Adaptive Server IQ
collation. The client side does not use a collation label. Different databases
on a database server may have different collation labels.
For more information, see “Understanding the locale collation label” on
page 328.
Understanding the locale language
The locale language is an indicator of the language being used by the user of
the client application, or expected to be used by users of the database server.
For a list of supported locale languages, see “Language label values” on page
325.
For how to find locale settings, see “Determining locale information” on page
345.
The client library or database server determines the language component of the
locale as follows:
1
It checks the SQLLOCALE environment variable, if it exists.
For more information, see “Setting the SQLLOCALE environment
variable” on page 328.
2
On Windows and Windows NT, it checks the Adaptive Server IQ language
registry entry.
3
On other operating systems, or if the registry setting is not present, it
checks the operating system language setting.
Summary of Contents for Adaptive Server IQ 12.4.2
Page 1: ...Administration and Performance Guide Adaptive Server IQ 12 4 2 ...
Page 16: ...xvi ...
Page 20: ...Related documents xx ...
Page 40: ...Compatibility with earlier versions 20 ...
Page 118: ...Troubleshooting startup shutdown and connections 98 ...
Page 248: ...Importing data by replication 228 ...
Page 306: ...Integrity rules in the system tables 286 ...
Page 334: ...Cursors in transactions 314 ...
Page 396: ...Users and permissions in the system tables 376 ...
Page 438: ...Determining your data backup and recovery strategy 418 ...
Page 484: ...Network performance 464 ...
Page 500: ...System utilities to monitor CPU use 480 ...
Page 514: ...Characteristics of Open Client and jConnect connections 494 ...
Page 536: ...Index 516 ...