@@ -8318,7 +8318,7 @@ Node-oracledb always uses Oracle's AL32UTF8 character set internally.
8318
8318
Data will be converted between AL32UTF8 and the
8319
8319
database character set when it is inserted into, or queried from, the
8320
8320
database. The environment variable ` NLS_LANG ` can be used to
8321
- configure the Oracle client language and territory only.
8321
+ configure the Oracle ' client' (i.e. node-oracledb) language and territory only.
8322
8322
8323
8323
Oracle NLS environment variables, or statements like ` ALTER SESSION ` ,
8324
8324
can be used to configure further aspects of node-oracledb data access
@@ -8327,6 +8327,24 @@ globalization. Examples are `NLS_NUMERIC_CHARACTERS` (discussed in
8327
8327
in [Fetching Numbers and Dates as String](#fetchasstringhandling)).
8328
8328
Refer to [NLS Documentation][69] for others.
8329
8329
8330
+ To find the database character set, execute the query:
8331
+
8332
+ ` ` ` sql
8333
+ SELECT value AS db_charset
8334
+ FROM nls_database_parameters
8335
+ WHERE parameter = ' NLS_CHARACTERSET'
8336
+ ` ` `
8337
+
8338
+ The general Oracle statement to find the 'client' character set is:
8339
+
8340
+ ` ` ` sql
8341
+ SELECT DISTINCT client_charset AS client_charset
8342
+ FROM v$session_connect_info
8343
+ WHERE sid = SYS_CONTEXT (' USERENV' , ' SID' );
8344
+ ` ` `
8345
+
8346
+ In node-oracledb this will always show AL32UTF8.
8347
+
8330
8348
## <a name="endtoend"></a> 21. End-to-end Tracing, Mid-tier Authentication, and Auditing
8331
8349
8332
8350
The Connection properties [action](#propconnaction),
0 commit comments