From: Hannu Krosing <hannu@trust.ee>
To: phd2@earthling.net
Cc: Thomas Lockhart <lockhart@alumni.caltech.edu>
Cc: 'Oleg Bartunov' <oleg@sai.msu.su>
Cc: 'hackers@postgresql.org' <hackers@postgreSQL.org>
Cc: Tatsuo Ishii <t-ishii@sra.co.jp>
Subject: Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem
Date: Sat, 12 Jun 1999 21:16:53 +0300
Message-ID: <3762A415.BC415D4C@trust.ee> (raw)
References: <Pine.LNX.4.04.9906121825030.28833-100000@emerald.netskate.ru>
Oleg Broytmann wrote:
>
> Hi!
>
> On Fri, 11 Jun 1999, Thomas Lockhart wrote:
> > > And what a pros and cons for NCHAR?
> > I was hoping you would tell me! :)
>
> I can see only one advantage for NCHAR - those fields that aren't NCHAR
> will not use strcoll() for comparison.
> But I cannot remember one filed in my database that does not contain
> russian characters. Even my WWW logs contain them.
what about the tables beginning with pg_ ?
Are the system tables currently affected by --enable-locale ?
> So in any case I am forced to make all my fields NCHAR, and this is
> exactly what we have now - postgres compiled with --enable-locale makes all
> char NCHAR.
Well, the problem is that while I do occasionally need cyrillic chars,
I also need English, Estonian, Finnish/Swedish, Latvian and Lithuanian.
The only two of them that don't have overlapping character codes are
Russian (all chars >127) and English (all < 128)
My current solution is to run without --enable-locale and do all the
sorting
in the client. But it would be often useful to have language specific
columns.
--------------------
Hannu
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: hannu@trust.ee, phd2@earthling.net, lockhart@alumni.caltech.edu, oleg@sai.msu.su, hackers@postgreSQL.org, t-ishii@sra.co.jp
Subject: Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem
In-Reply-To: <3762A415.BC415D4C@trust.ee>
* 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