From 703fa735129517423aaa32acc92ea0aa8edabbcc Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 23 Sep 2024 09:51:26 +0530 Subject: [PATCH] Added blank spaces --- .../nls_functions/index.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/epas/17/reference/sql_reference/03_functions_and_operators/nls_functions/index.mdx b/product_docs/docs/epas/17/reference/sql_reference/03_functions_and_operators/nls_functions/index.mdx index 59f404cfb28..b996a751b3f 100644 --- a/product_docs/docs/epas/17/reference/sql_reference/03_functions_and_operators/nls_functions/index.mdx +++ b/product_docs/docs/epas/17/reference/sql_reference/03_functions_and_operators/nls_functions/index.mdx @@ -124,18 +124,18 @@ NOTICE: pg collation not found for entry (XGERMAN,abc) in nls config file at li It's important to recognize that collation values are platform-dependent, meaning a collation available on one platform might not be present on another. To avoid compatibility issues, always use collations that are available in the `pg_collation` table within your environment. -Each client session reads the config file and stores the NLS parameters and collation values in in-memory HASH data structure when any of the NLS function is called for the first time.The parsing logic will read each row sequentially, segregate NLS parameters and collation values, and then store them in the right data structure. +Each client session reads the config file and stores the NLS parameters and collation values in in-memory HASH data structure when any of the NLS function is called for the first time. The parsing logic will read each row sequentially, segregate NLS parameters and collation values, and then store them in the right data structure. -Making changes to the config file manually requires you to reload the NLS config files in all sessions or restart the session to work with the updated mappings.Using the `edb_nls_cf_insert` function to modify the config file in a session will update the in-memory HASH data structure with new mappings. Changes made in a session will only affect other sessions after the config file is reloaded or after the other sessions are restarted. +Making changes to the config file manually requires you to reload the NLS config files in all sessions or restart the session to work with the updated mappings. Using the `edb_nls_cf_insert` function to modify the config file in a session will update the in-memory HASH data structure with new mappings. Changes made in a session will only affect other sessions after the config file is reloaded or after the other sessions are restarted. The available functions for managing the NLS config file are listed in the following table: -| Function | Return type | Description | -|-----------------------------------------------------------|-------------|------------------------------------------------------------------------------------------------------------------| -| `edb_nls_cf_insert(nls TEXT, collation TEXT)` | VOID | Adds a new mapping in the NLS config file with the given NLS parameter and a mapping collation. | +| Function | Return type | Description | +|-----------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------| +| `edb_nls_cf_insert(nls TEXT, collation TEXT)` | VOID | Adds a new mapping in the NLS config file with the given NLS parameter and a mapping collation. | | `edb_nls_cf_reload()` | VOID | Reloads the NLS config file and updates the NLS parameter and a mapping collation in in-memory HASH data structure. | -| `edb_nls_cf_hash_dump(OUT nls TEXT, OUT collationid INT)` | RECORD | Dumps the NLS parameter and a mapping collation HASH contents on the client session. | -| `edb_nls_cf_dump(OUT nls TEXT, OUT collation TEXT)` | RECORD | Dumps the existing NLS config file contents on the client session. | +| `edb_nls_cf_hash_dump(OUT nls TEXT, OUT collationid INT)` | RECORD | Dumps the NLS parameter and a mapping collation HASH contents on the client session. | +| `edb_nls_cf_dump(OUT nls TEXT, OUT collation TEXT)` | RECORD | Dumps the existing NLS config file contents on the client session. | **Supported NLS functions**