gustafn
committed
on 20 Jul
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 PostgreSQL

Previously, our localization script always queried the Oracle‐specific

view `v$nls_valid_values`. On PostgreSQL this table doesn’t exist, so

the DB driver logged a misleading “relation does not exist” error.

Now, we only perform that query when connected to Oracle. For all other

DBs (e.g. PostgreSQL) we skip it, eliminating spurious errors from

the logs.

In the the futures, one should introduce a new API call named in the

lines of "get_NLS_Info" that encapsulates the database‐specific logic

for determining language, charset, and territory.

Show less