However, if the locale that your database needs isn't available, what did
you intend to do about that? You can't just pick a different one, it
probably wouldn't behave the same. Apparently you can't just use the
default locales either, or you wouldn't be asking about this.
I'm trying to create portable application which can automatically create
database using estonian locale in any server.
Postgres returns different values for same locale:
In Fedora et_EE.UTF8
Other linuxes et_EE.UTF-8
In Windows Estonian_Estonia.1257
In some other Linuxes something like Estonian.Estonia
For this reason I'm looking for a way to probe server for locale existence.
If the locale you need isn't available on the server and you don't have
shell access to it, then you'll have to contact the server administrators
to _make_ the locale available.
That means that either the OS doesn't have the required locale, or the
database cluster was initialised with an incompatible default locale -
neither of these situations can be solved by trying CREATE DATABASE with a
different locale, not if the locale mattered in the first place.
My locale may be available but it can have at least four different values
depending on server.
No need to disturb admins.
Andrus.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
