| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: per db collate syntax |
| Date: | 2009-04-21 17:42:51 |
| Message-ID: | 49EE059B.9050507@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jaime Casanova wrote:
> I was trying to create a database and found that we are using
> LC_COLLATE and LC_CTYPE, why not simply COLLATE and CTYPE?
This was discussed recently, and in fact changed from COLLATE/CTYPE to
LC_COLLATE/LC_CTYPE. The reason is that LC_COLLATE and LC_CTYPE makes
it more clear that the options set the LC_COLLATE and LC_CTYPE
environment variables. There is also precedent: the pre-existing initdb
options were called --lc-collate and --lc-ctype, so the new createdb
options are quite naturally also called --lc-collate and --lc-ctype, and
since they're called that, it would be weird if the CREATE DATABASE
options had different names.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-04-21 18:18:00 | Re: Automating Partitions in PostgreSQL - Query on syntax |
| Previous Message | Robert Haas | 2009-04-21 17:38:33 | Re: Automating Partitions in PostgreSQL - Query on syntax |