Re: Thoughts on multiple simultaneous code page support

From: Giles Lean <giles(at)nemeton(dot)com(dot)au>
To: "Randall Parker" <randall(at)nls(dot)net>
Cc: "PostgreSQL-Dev" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Thoughts on multiple simultaneous code page support
Date: 2000-06-22 01:17:14
Message-ID: 11907.961636634@nemeton.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> 1) Make the entire database Unicode
> ...
> It also makes sorting and indexing take more time.

Mentioned in my other email, but what collation order were you
proposing to use? Binary might be OK for unique keys but that doesn't
help you for '<', '>' etc.

My expectation (not the same as I'd like to see, necessarily, and not
that my opinion counts -- I'm not a developer) would be that each
database have a locale, and that this locale's collation order be used
for indexing, LIKE, '<', '>' etc. If you want to store data from
multiple human languages using a locale that has Unicode for its
character set would be appropriate/necessary.

Regards,

Giles

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2000-06-22 01:27:26 RE: Big 7.1 open items
Previous Message Hiroshi Inoue 2000-06-22 01:15:01 RE: Big 7.1 open items