Re: multibyte support by default - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: multibyte support by default
Date
Msg-id 20020417110929G.t-ishii@sra.co.jp
Whole thread Raw
In response to Re: multibyte support by default  (Hannu Krosing <hannu@tm.ee>)
List pgsql-hackers
> On Tue, 2002-04-16 at 03:20, Tatsuo Ishii wrote:
> > In my understanding, our consensus was enabling multibyte support by
> > default for 7.3. Any objection?
> 
> Is there currently some agreed plan for introducing standard
> NCHAR/NVARCHAR types.

I have such a kind of *personal* plan, maybe for 7.4, not for 7.3 due
to the limitation of my free time.

BTW, NCHAR/NVARCHAR is just a abbreviation of "CHAR(n) CHARACTER SET
foo"(where foo is an implementaion defined charset). So I'm not too
impressed by an idea implementing NCHAR/NVARCHAR alone.

> What does ISO/ANSI say about multybyteness of simple CHAR types ?

There's no such that idea "multybyteness" in the standard.  In my
understanding the standard does not restrict "normal" CHAR types to
have only ASCII (more precisely "SQL_CHARACTER"). Moreover, CHAR types
without CHARSET specification will a have default charset to SQL_TEXT,
and its actual charset will be defined by the implementation.

In summary allowing any characters including multibyte ones in CHAR
types is not againt the standard at all, IMO.
--
Tatsuo Ishii


pgsql-hackers by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Index Scans become Seq Scans after VACUUM ANALYSE
Next
From: "Rod Taylor"
Date:
Subject: Re: [BUGS] Foreign Key woes -- 7.2 and ~7.3