From: Dmitry Samersoff <dms@wplus.net>
To: Oleg Broytmann <phd@emerald.netskate.ru>
Cc: Tatsuo Ishii <t-ishii@sra.co.jp>
Cc: hackers@postgresql.org <hackers@postgresql.org>
Cc: Oleg Bartunov <oleg@sai.msu.su>
Cc: Thomas Lockhart <lockhart@alumni.caltech.edu>
Subject: Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem
Date: Fri, 11 Jun 1999 11:27:49 +0400 (MSD)
Message-ID: <XFMail.990611112749.dms@wplus.net> (raw)
In-Reply-To: <Pine.LNX.4.04.9906111111001.16461-100000@emerald.netskate.ru>
On 11-Jun-99 Oleg Broytmann wrote:
> On Thu, 10 Jun 1999, Thomas Lockhart wrote:
>> istm that the Russian and Japanese contingents could represent the
>> needs of multibyte and locale concerns very well. So, we should ask
>> ourselves some questions to see if we can make *progress* in evolving
>> our text handling, rather than just staying the same forever.
>
> Ok, we are here.
> And what a pros and cons for NCHAR?
>
>> SQL92 suggests some specific text handling features to help with
>> non-ascii applications. "national character" is, afaik, the feature
>
> What the help?
>
>> which would hold an installation-wide local text type. "collations"
>> would allow other text types in the same installation, but SQL92 is a
>> bit fuzzier about how to make them work.
>>
>> Would these mechanisms work for people? Or are they so fundamentally
>> flawed or non-standard (it is from a standard, but I'm not sure who
>> implements it)?
There are two different problems under "locale" cover.
First is national charset handling, mostly sorting,
I try to find official recomendation for it.
Another one is encoding conversion -
it's unlimited field for discussion.
IMHO, conversion table have to be stored on per host basic,
some where near from HBA.
Sort table is to be placed near from createdb.
Custom sort table is also very attractive for me.
---
Dmitry Samersoff, dms@wplus.net, ICQ:3161705
http://devnull.wplus.net
* There will come soft rains ...
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: dms@wplus.net, phd@emerald.netskate.ru, t-ishii@sra.co.jp, hackers@postgresql.org, oleg@sai.msu.su, lockhart@alumni.caltech.edu
Subject: Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem
In-Reply-To: <XFMail.990611112749.dms@wplus.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox