Re: Multibyte encoding vs. SQL_ASCII vs. locales and European languages

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Frank Joerdens <frank(at)joerdens(dot)de>
Cc: Frank Schafer <frank(dot)schafer(at)setuza(dot)cz>, pgsql-general(at)postgresql(dot)org
Subject: Re: Multibyte encoding vs. SQL_ASCII vs. locales and European languages
Date: 2002-01-29 15:56:37
Message-ID: 14299.1012319797@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Frank Joerdens <frank(at)joerdens(dot)de> writes:
> Multibyte support is mainly recommended for character sets that don't
> fit into a single byte (Chinese, Japanese, Korean), and locale support
> is said to be mostly sufficient for European languages . . . what escapes
> me is why I should bother with either of these when SQL_ASCII works just
> fine with my mostly German users. I must be missing something, right?

Sort ordering of non-7-bit-ASCII characters? upper/lower case
conversions that work as expected? locale-aware formatting options
in to_char and friends?

If you don't need any of that, then you won't need locale support.

I agree that you have no use for multibyte support.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrew Sullivan 2002-01-29 16:22:56 Re: Moving my business to PostgreSQL
Previous Message Peter Darley 2002-01-29 15:47:21 Re: Moving my business to PostgreSQL