Avoid noisy “table not found” errors on PostgreSQL
Previously, our localization script always queried the Oracle‐specific view `v$nls_valid…
Show more
Avoid noisy “table not found” errors on PostgreSQLPreviously, our localization script always queried the Oracle‐specificview `v$nls_valid_values`. On PostgreSQL this table doesn’t exist, sothe DB driver logged a misleading “relation does not exist” error.Now, we only perform that query when connected to Oracle. For all otherDBs (e.g. PostgreSQL) we skip it, eliminating spurious errors fromthe logs.In the the futures, one should introduce a new API call named in thelines of "get_NLS_Info" that encapsulates the database‐specific logicfor determining language, charset, and territory.
Show less