| From: | t-ishii(at)sra(dot)co(dot)jp |
|---|---|
| To: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | "Jose' Soares Da Silva" <sferac(at)bo(dot)nettuno(dot)it>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, phd2(at)earthling(dot)net, Postgres Hackers List <hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] Postgres-6.3.2 locale patch |
| Date: | 1998-06-16 04:47:33 |
| Message-ID: | 199806160447.NAA29579@srapc451.sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>When a database is created, it can be specified with a default character
>set/collation sequence for the database; this would correspond to the
>NCHAR/NVARCHAR/NTEXT types. We could implement a
> SET NATIONAL CHARACTER SET = 'language';
In the current implementation of MB, the encoding used by BE is
determined at the compile time. This time I would like to add more
flexibility in that the encoding can be specified when creating a
database. I would like to add a new option to the CREATE DATABASE
statement:
CREATE DATABASE WITH ENCODING 'encoding';
I'm not sure if this kind of thing is defined in the
standard. Suggestion?
--
Tatsuo Ishii
t-ishii(at)sra(dot)co(dot)jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Gould | 1998-06-16 05:35:30 | Re: [HACKERS] [Fwd: [ANNOUNCE] ipaddr data type - EXTENDED VERSION HERE] |
| Previous Message | Bruce Momjian | 1998-06-16 04:32:49 | Re: [HACKERS] [Fwd: [ANNOUNCE] ipaddr data type - EXTENDED VERSION HERE] |