Re: [PATCHES] Postgres-6.3.2 locale patch - Mailing list pgsql-hackers

From t-ishii@sra.co.jp
Subject Re: [PATCHES] Postgres-6.3.2 locale patch
Date
Msg-id 199806160447.NAA29579@srapc451.sra.co.jp
Whole thread Raw
In response to Re: [PATCHES] Postgres-6.3.2 locale patch  ("Thomas G. Lockhart" <lockhart@alumni.caltech.edu>)
List 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@sra.co.jp

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] [Fwd: [ANNOUNCE] ipaddr data type - EXTENDED VERSION HERE]
Next
From: dg@illustra.com (David Gould)
Date:
Subject: Re: [HACKERS] [Fwd: [ANNOUNCE] ipaddr data type - EXTENDED VERSION HERE]