important that you specify the encoding and the locale.
Otherwise it will fail and report that the locale is invalid.
--
Kent Tong
SME accounting software package for just MOP30.
See
http://www.cpttm.org.mo/index_c.php?pg=cpttm/department/is/ispu/accsys/index.htm
for more.
--
Sent via pgsql
Peter Eisentraut wrote:
On a POSIX system, you can do
$ LC_ALL= locale charmap
and verify manually that the printed charmap (= character set encoding)
matches what you use in PostgreSQL. I don't know whether an equivalent
interface exists on Windows.
Right, there is no such command.
Reading and
Peter Eisentraut wrote:
Here is a test (run in pgadmin III):
1. createdb db1 -E Unicode
Probably your locale does not support Unicode. You need to pick an
encoding that matches your locale or vice versa.
Is there any way to check?
I have other programs reading and writing Unicode on this
compute
Hi,
I'm running PostgreSQL v8 beta4 on Win2K. The default language
selected in Win2K is Big5.
I am using the Windows installer to install it. Everything is
left as default except that the locale for initdb is set to
"traditional-chinese".
Here is a test (run in pgadmin III):
1. createdb db1 -E Unic
:
initdb --locale zh_TW.utf8 /var/lib/pgsql/data
then it works fine!
Thanks again and sorry about any inconvenience.
--
Kent Tong, Msc, MCSE, SCJP, CCSA, Delphi Certified
Manager of IT Dept, CPTTM
Authorized training for Borland, Cisco, Microsoft, Oracle, RedFlag & RedHat
data.
Does it matter? The encoding provided to initdb is just
a default for the databases to be created in the future.
When I used createdb, I did specify "-E unicode".
--
Kent Tong, Msc, MCSE, SCJP, CCSA, Delphi Certified
Manager of IT Dept, CPTTM
Authorized training for Borland, C
