From: | "CN" <cnliou9(at)fastmail(dot)fm> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Please change default characterset for database cluster |
Date: | 2007-09-29 01:00:10 |
Message-ID: | 1191027610.19606.1213196447@webmail.messagingengine.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi!
"initdb" use SQL_ASCII as the default characterset encoding when it is
not given option "-E" and when it can not correctly derive one from
locale. I suggest "initdb" use UNICODE instead of SQL_ASCII because
UNICODE is far more useful than SQL_ASCII.
Not all webmasters are willing to spend time reading "initdb"
documentation. I have encountered a free web hosting providing
PhpPgAdmin through which I can create my databases. Problem is that all
newly created databases use SQL_ASCII which is completely useless to me.
Their PhpPgAdmin script does not support "-E" switch for "createdb". As
a result, I have to abandon that service all together. Was "initdb"
using UNICODE as the default characterset, everthing would be perfect.
Regards,
CN
--
http://www.fastmail.fm - Same, same, but different
From | Date | Subject | |
---|---|---|---|
Next Message | Carlos Moreno | 2007-09-29 01:32:43 | Re: Please change default characterset for database cluster |
Previous Message | Scott Marlowe | 2007-09-29 00:17:15 | Re: more problems with count(*) on large table |