Re: Unicode combining characters

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: ZeugswetterA(at)spardat(dot)at, pgman(at)candle(dot)pha(dot)pa(dot)us, phede-ml(at)islande(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Unicode combining characters
Date: 2001-10-04 03:43:23
Message-ID: 20011004124323U.t-ishii@sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

> What's your feeling now about the original question: whether to enable
> multibyte by default now, or not? I'm still thinking that Peter's
> counsel is the wisest: plan to do it in 7.3, not today. But this fix
> seems to eliminate the only hard reason we have not to do it today ...

If SQL99's I18N staffs would be added in 7.3, it means both the
multibyte support and the locale support might disappear, then 2might
be merged into it (not sure about NLS. is that compatible with, for
example, per column charset?)

So, for none multibyte users, the multibyte support would be
one-release-only-functionality: suddenly appears in 7.2 and disappears
in 7.3. I'm afraid this would cause more troubles rather than
usefullness.

What do you think?
--
Tatsuo Ishii

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-10-04 03:49:49 Re: Unicode combining characters
Previous Message Mark Pritchard 2001-10-04 03:25:21 Re: Feature suggestion: Postgresql binding to one IP?

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2001-10-04 03:49:49 Re: Unicode combining characters
Previous Message Tom Lane 2001-10-04 03:05:16 Re: Unicode combining characters